[LU-12317] sanity test 239a fails with 'test_59 failed with 1' Created: 20/May/19 Updated: 01/Jul/19 Resolved: 01/Jul/19 |
|
| Status: | Closed |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.13.0, Lustre 2.12.1, Lustre 2.12.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | James Nunez (Inactive) | Assignee: | WC Triage |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | dne, zfs | ||
| Environment: |
ZFS/DNE |
||
| Issue Links: |
|
||||||||
| Severity: | 3 | ||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||
| Description |
|
sanity test_239a fails with 'test_59 failed with 1' for ZFS/DNE testing only. We’ve seen this test fail seven times since February and it looks like this test started failing with this error on 2019-02-20 with logs at https://testing.whamcloud.com/test_sets/299f3fba-358b-11e9-ae87-52540065bddc . Looking at a recent failure, https://testing.whamcloud.com/test_sets/6a2b64a6-759a-11e9-a6f9-52540065bddc, we see that the test is failing because the delete did not complete in the 30 second time limit with some debug information following it. From the suite_log, we see Delete is not completed in 30 seconds CMD: trevis-48vm8 /usr/sbin/lctl get_param osc.*MDT*.sync_* osc.lustre-OST0000-osc-MDT0000.sync_changes=0 osc.lustre-OST0000-osc-MDT0000.sync_in_flight=0 osc.lustre-OST0000-osc-MDT0000.sync_in_progress=0 osc.lustre-OST0000-osc-MDT0002.sync_changes=0 osc.lustre-OST0000-osc-MDT0002.sync_in_flight=0 osc.lustre-OST0000-osc-MDT0002.sync_in_progress=0 osc.lustre-OST0001-osc-MDT0000.sync_changes=0 osc.lustre-OST0001-osc-MDT0000.sync_in_flight=0 osc.lustre-OST0001-osc-MDT0000.sync_in_progress=624 osc.lustre-OST0001-osc-MDT0002.sync_changes=0 osc.lustre-OST0001-osc-MDT0002.sync_in_flight=0 osc.lustre-OST0001-osc-MDT0002.sync_in_progress=0 osc.lustre-OST0002-osc-MDT0000.sync_changes=0 osc.lustre-OST0002-osc-MDT0000.sync_in_flight=0 osc.lustre-OST0002-osc-MDT0000.sync_in_progress=0 osc.lustre-OST0002-osc-MDT0002.sync_changes=0 osc.lustre-OST0002-osc-MDT0002.sync_in_flight=0 osc.lustre-OST0002-osc-MDT0002.sync_in_progress=0 osc.lustre-OST0003-osc-MDT0000.sync_changes=0 osc.lustre-OST0003-osc-MDT0000.sync_in_flight=0 osc.lustre-OST0003-osc-MDT0000.sync_in_progress=625 osc.lustre-OST0003-osc-MDT0002.sync_changes=0 osc.lustre-OST0003-osc-MDT0002.sync_in_flight=0 osc.lustre-OST0003-osc-MDT0002.sync_in_progress=0 osc.lustre-OST0004-osc-MDT0000.sync_changes=0 osc.lustre-OST0004-osc-MDT0000.sync_in_flight=0 osc.lustre-OST0004-osc-MDT0000.sync_in_progress=0 osc.lustre-OST0004-osc-MDT0002.sync_changes=0 osc.lustre-OST0004-osc-MDT0002.sync_in_flight=0 osc.lustre-OST0004-osc-MDT0002.sync_in_progress=0 osc.lustre-OST0005-osc-MDT0000.sync_changes=0 osc.lustre-OST0005-osc-MDT0000.sync_in_flight=0 osc.lustre-OST0005-osc-MDT0000.sync_in_progress=626 osc.lustre-OST0005-osc-MDT0002.sync_changes=0 osc.lustre-OST0005-osc-MDT0002.sync_in_flight=0 osc.lustre-OST0005-osc-MDT0002.sync_in_progress=0 osc.lustre-OST0006-osc-MDT0000.sync_changes=0 osc.lustre-OST0006-osc-MDT0000.sync_in_flight=0 osc.lustre-OST0006-osc-MDT0000.sync_in_progress=626 osc.lustre-OST0006-osc-MDT0002.sync_changes=0 osc.lustre-OST0006-osc-MDT0002.sync_in_flight=0 osc.lustre-OST0006-osc-MDT0002.sync_in_progress=0 osc.lustre-OST0007-osc-MDT0000.sync_changes=0 osc.lustre-OST0007-osc-MDT0000.sync_in_flight=0 osc.lustre-OST0007-osc-MDT0000.sync_in_progress=625 osc.lustre-OST0007-osc-MDT0002.sync_changes=0 osc.lustre-OST0007-osc-MDT0002.sync_in_flight=0 osc.lustre-OST0007-osc-MDT0002.sync_in_progress=0 sanity test_239a: @@@@@@ FAIL: test_239a failed with 1 We don’t see any errors or anything that indicates an issue in any node console log. The following are links to failed test suite logs not mentioned above |
| Comments |
| Comment by Vitaly Fertman [ 30/Jun/19 ] |
|
a dup of LU-11987? |
| Comment by James Nunez (Inactive) [ 01/Jul/19 ] |
|
Closing ticket because, as Vitaly pointed out, this looks like a duplicate of LU-11987. |