[LU-8688] All Lustre test suites should run/PASS with separate MDS and MGS

• Type: Task
• Resolution: Unresolved
• Priority: Minor
• Labels: tests
• Assignee: WC Triage
• Reporter: James Nunez (Inactive)

Description

Since separate MDS and MGS is a common and recommended Lustre set-up, full test group and patch testing should be run against this Lustre configuration. We can request a separate MDT and MGT (both on the same node/VM) for autotesting by using ‘Test-Parameters: combinedmdsmgs=false’ in a patch commit message and, thus, we are able to test separate targets (only separate targets and not separate nodes).

The purpose of this ticket is to track the various efforts/tickets that are working to get the Lustre test suites running on separate MDS and MGS.

Issue Links

• is related to: LU-14799 make conf-sanity support separate MGS servers
• is related to: LU-9400 conf-sanity test 103 hangs with separate MGS and MDS
• is related to: LU-9406 conf-sanity test 82b fails with ‘FAIL: /usr/sbin/lctl pool_add scratch.test_82b scratch-OST[*] failed’
• is related to: LU-9875 conf-sanity test 70e fails with 'start mdt1 failed'
• is related to: LU-9879 conf-sanity test 80 fails with “Failed to start MDT”
• is related to: LU-8108 Separated MGS/MDS: conf-sanity test_32a: Unable to mount (-114)
• is related to: LU-625 sanityn test_32a test failure
• is related to: LU-7529 conf-sanity test_32a fails when using seperate MGS
• is related to: LU-8110 Seperated MGS/MDS: conf-sanity test_32a: MGS doesn't stop before test starts
• is related to: LU-8473 conf-sanity test_41a with separate MGS stuck on starting client and timed out
• is related to: LU-8474 conf-sanity test_55 with separate MGS stuck on starting client and timed out
• is related to: LU-8550 problems of conf-sanity test_32
• is related to: LU-8552 Problems of testing with a separated MGS in conf-sanity.sh:
• is related to: LU-8687 Fix test-framework.sh for ost-pools suite in case of separate MGS/MDS setup
• is related to: LU-8701 scrub-performance defect: suite is not functional on config with not combined mgs mds
• is related to: LU-9014 conf-sanity test_72() fails with a separate MGS and MDT
• is related to: LU-9860 conf-sanity test_33a fails with “mount -t lustre failed“ for separate MDS and MGS
• is related to: LU-9899 Lustre test suites need a client on the MGS when MGS on separate node from MDS
• is related to: LU-7435 ost-pools defect: suite is not functional on config MGS/MDS not combined
• is related to: LU-8109 Separated MGS/MDS: conf-sanity test_32a: Unable to mount (-114)