[LU-3793] conf-sanity, subtest test_66 fails due to previous state Created: 20/Aug/13  Updated: 22/Sep/23  Resolved: 09/Jan/20

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.5.0
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Maloo Assignee: WC Triage
Resolution: Low Priority Votes: 1
Labels: None

Issue Links:
Related
is related to LU-11990 conf-sanity test_66: replace nids fai... Reopened
is related to LU-3938 Test failure on test suite conf-sanit... Resolved
is related to LU-5137 Test failure conf-sanity test_66: rep... Resolved
is related to LU-3056 conf-sanity test_66 - replace nids fa... Resolved
is related to LU-3794 conf-sanity test_73: 1st tunefs failed Resolved
Severity: 3
Rank (Obsolete): 9810

 Description   

This issue was created by maloo for Nathaniel Clark <nathaniel.l.clark@intel.com>

This issue relates to the following test suite run: http://maloo.whamcloud.com/test_sets/effa4886-0980-11e3-901c-52540035b04c.

The sub-test test_66 failed with the following error:

MDT start failed

Info required for matching: conf-sanity 66

If test_61 fails (a la LU-3792) then the state is left partially up, and the setup call in 66 will fail.

 Comments   
Comment by Andreas Dilger [ 21/Aug/13 ]

The goal of this ticket should be to make conf-sanity more robust about resetting the state in the face of failures. Unfortunately, this should take a lower priority than actually fixing the real test failures, since we can never land a patch that has any failures, and ideally we would never see failures and this issue would be moot.

Comment by Andreas Dilger [ 09/Jan/20 ]

Close old bug

Generated at Sat Feb 10 01:36:57 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.