[LU-9899] Lustre test suites need a client on the MGS when MGS on separate node from MDS

• Type: Bug
• Resolution: Duplicate
• Priority: Minor
• Affects Version/s: Lustre 2.10.0, Lustre 2.11.0
• Labels: tests
• Severity: 3
• Assignee: James Nunez (Inactive)
• Reporter: James Nunez (Inactive)

Description

When running testing on a Lustre configuration with a separate MGS and MDS, we need to mount the file system on the MGS so that the lctl command can look in /proc/fs/lustre/*/lov/pools to get the current state of OST pools.

We need modify several test scripts or individual tests to mount the file system on the MGS. Tests that manipulate OST pools are:
sanity: 27D, 200, 253, 406
replay-single: 85b
conf-sanity: 82b, 103
ost_pools: All tests

Logs for the master patch review test sessions when run against a Lustre file system with separate MGS and MDS are at
review-zfs-part-1 - https://testing.hpdd.intel.com/test_sessions/a301d35c-6b13-4ec5-8258-01c7512a8b92
review-zfs-part-2 - https://testing.hpdd.intel.com/test_sessions/7571cc45-7447-409e-98d3-e1cf649018d9
review-dne-part-1 - https://testing.hpdd.intel.com/test_sessions/e949626a-2945-4ff0-bad2-af48ee45c6ed
review-dne-part-2 - https://testing.hpdd.intel.com/test_sessions/0bd12b68-eeaa-4b95-ac20-ed64590ccd9e

Issue Links

• duplicates: LU-11743 lctl pool operations cannot be run on separate MGS system
• is related to: LU-8688 All Lustre test suites should run/PASS with separate MDS and MGS