Details
-
Bug
-
Resolution: Fixed
-
Major
-
Lustre 2.7.0
-
None
-
Autotest
-
3
-
16396
Description
In conf-sanity, each test is called from a wrapper function run_test(). When the test completes, run_test() eventually calls check_catastrophe. For some tests, check_catastrophe() does not complete correctly:
02:31:40:CMD: onyx-38vm3,onyx-38vm4,onyx-38vm5 rc=\$(lctl get_param -n catastrophe);
02:31:40: if [ \$rc -ne 0 ]; then echo \$(hostname): \$rc; fi
02:31:40: exit \$rc
02:31:40:onyx-38vm5: error: get_param: /proc/{fs,sys}/{lnet,lustre}/catastrophe: Found no match
02:31:40:onyx-38vm5: sh: line 1: [: -ne: unary operator expected
For example, conf-sanity tests 53a, 53b, 56, 57a, 58, 61, 62, 66, 67 and others at https://testing.hpdd.intel.com/test_sets/5634cf00-6375-11e4-b5da-5254006e85c2 have these errors during the test clean up in the call to check_catastrophe.
More of these error messages in conf-sanity can be found at:
https://testing.hpdd.intel.com/test_sets/20be82f6-637c-11e4-80e1-5254006e85c2
The test is correctly marked as pass or fail regardless of if check_catastrophe works or not.