test_130a and test_130e fail together whenever OSTCOUNT > 9:

test_130a: OST10 was reported on OST 000a
test_130e: OST 000d 1 != 2

Root cause: both tests compare the OST index from '$LFS getstripe -i' (plain decimal) against the OST index parsed out of 'filefrag -ve' output (zero-padded 4-digit, e.g. 000a, 000d) using bash '(( ))' arithmetic. Bash treats a leading-zero operand as octal, so any padded index containing digit 8/9 or a hex letter a-f is not a valid octal/decimal literal: the '(( ))' evaluation itself errors out. In test_130a this makes the equality test spuriously fail; in test_130e it makes the enclosing 'if (( $frag_lun != $last_lun ))' silently skip its body, so num_luns never reaches 2. This only shows up once OSTCOUNT exceeds 9 (single-digit indices are octal-safe by luck), which ordinary conf-sanity/sanity runs never do. This change's own Test-Parameters (osscount=2) bring up 16 OSTs, which is why it surfaces here.

Not this patch's: the diff under review only touches test-framework.sh/functions.sh node-list helpers (nodes_list, facets_nodes, etc.); it makes no change to sanity.sh's test_130a/test_130e. The same failure signature (OST index >= 8 breaking these comparisons) was already reported against sanity test_130a/130d/130e in 2012 (LU-2004, resolved as duplicate), so this predates the patch by well over a decade.

Maloo: https://testing.whamcloud.com/test_sets/2d145c50-18a5-46a6-aaec-ead9ddd73f0f (test_130a, test_130e)

Raised by Patch Watcher run pw-engineer-51976-ps6-684d26660414 on https://review.whamcloud.com/51976