[LU-13243] sanity test 183 fails with 'ls succeeded, should have failed'

• Type: Bug
• Resolution: Unresolved
• Priority: Minor
• Affects Version/s: Lustre 2.14.0
• Labels: ppc
• Environment: PPC clients
• Severity: 3
• Assignee: WC Triage
• Reporter: James Nunez (Inactive)

Description

sanity test_183 fails with 'ls succeeded, should have failed' starting on 27 SEPT 2019 and fails 100% of the time for PPC client testing.

Looking at a recent failure at https://testing.whamcloud.com/test_sets/d3720002-4a27-11ea-b69a-52540065bddc, the suite_log the test output

== sanity test 183: No crash or request leak in case of strange dispositions ========================= 01:26:06 (1581125166)
CMD: trevis-10vm12 /usr/sbin/lctl set_param fail_loc=0x148
fail_loc=0x148
total 4
-rw-r--r-- 1 root root 4 Feb  8 01:26 f183.sanity
 sanity test_183: @@@@@@ FAIL: ls succeeded, should have failed 
  Trace dump:
  = /usr/lib64/lustre/tests/test-framework.sh:6121:error()
  = /usr/lib64/lustre/tests/sanity.sh:15012:test_183()
 

There are no errors or any indication of why this test fails in any of the console logs.

The code that is failing is

14998         mkdir -p $DIR/$tdir || error "creating dir $DIR/$tdir"
14999         echo aaa > $DIR/$tdir/$tfile
15000 
15001 #define OBD_FAIL_MDS_NEGATIVE_POSITIVE  0x148
15002         do_facet $SINGLEMDS $LCTL set_param fail_loc=0x148
15003 
15004         ls -l $DIR/$tdir && error "ls succeeded, should have failed"
 

Logs for more sanity test 183 failures are at
https://testing.whamcloud.com/test_sets/6a18091c-233a-11ea-bb75-52540065bddc
https://testing.whamcloud.com/test_sets/66d1b122-fd65-11e9-bbc3-52540065bddc