[LU-9879] conf-sanity test 80 fails with “Failed to start MDT”

• Type: Bug
• Resolution: Duplicate
• Priority: Minor
• Affects Version/s: Lustre 2.11.0
• Labels: tests
• Environment: Separate MDS and MGS or separate MDT and MGT
• Severity: 3
• Assignee: WC Triage
• Reporter: James Nunez (Inactive)

Description

When run with a separate MGS and MDS or MGT and MDT, conf-sanity test_80 fails with

conf-sanity test_80: @@@@@@ FAIL: Failed to start MDT 

When test 80 is run alone and all servers are already mounted, then the test will pass. If test 80 is run in sequence with all the other conf-sanity tests and there is a separate MGS and MDS, then the test fails because, the first thing is does is try to mount the MDS. The test does not consider if there is a separate MGS or not.

One fix for this issue is to change call start_mgsmds() instead of start_mds().

Other conf-sanity test may suffer from this same issue; test 84 and 100 are examples.

Related to this, there are some tests that start an MDT, with start_mdt(), but need to start the MGS, start_mgs(),first. conf-sanity test 87, 104, 105 and 107 are examples of this.

Logs for this test failure are at
https://testing.hpdd.intel.com/test_sets/39fe026c-8068-11e7-8825-5254006e85c2

Issue Links

• is related to: LU-10717 several conf-sanity tests failed: FAIL: start mgs failed
• is related to: LU-8688 All Lustre test suites should run/PASS with separate MDS and MGS