[LU-15242] sanity test_161d: FAIL: cat failed

• Status: Open
• Project: Lustre
• Type: Bug
• Priority: Minor
• Reporter: Maloo
• Assignee: WC Triage
• Resolution: Unresolved
• Severity: 3

Description

This issue was created by maloo for Elena <[e-mail]>

This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/47cb9645-e620-460d-bda5-195bcac531f0

test_161d failed with the following error:

cat failed

sanity test_161d regulary fails with:

Registered 4 changelog users: 'cl23 cl23 cl23 cl3'
fail_loc=0x8000140c
fail_val=5
    PID TTY          TIME CMD
 820133 ?        00:00:00 bash
 sanity test_161d: @@@@@@ FAIL: cat failed

VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
sanity test_161d - cat failed

Comments

[Andreas Dilger]

It looks like this has been failing for a long time, so it isn't easy to attribute it to a specific patch, and it may be that the subtest has been failing since it was first added. Given the large number of different failure modes for this test, I suspect it is just a flakey test that depends too much on timing to work reliably.

I searched back in the test results. It has failed 15 times in the past 4 weeks, and going back further to 2020-01-01 I found 74 failures with this message in 2020, and 45 in 2021, but the distribution is quite uneven (e.g. there were no failures between 2021-05-30 and 2021-08-01, even though this subtest was run thousands of times between those dates).

It would be useful to improve the "cat failed" message to remove the redirection to /dev/null to see if the FID could be extracted from the Changelog properly, and what error message "cat" is returning.

[Artem Blagodarenko (Inactive)]

+1 https://testing.whamcloud.com/test_sets/ee198b48-5a07-46c7-9546-3c4848269c02