[LU-8474] conf-sanity test_55 with separate MGS stuck on starting client and timed out

• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.9.0
• Affects Version/s: Lustre 2.9.0
• Severity: 3
• Assignee: Jian Yu
• Reporter: Jian Yu

Description

While running conf-sanity test 55 with separate MGT and MDT devices, it failed as follows:

Starting mgs:   /dev/vda5 /mnt/lustre-mgs
CMD: eagle-38vm3 mkdir -p /mnt/lustre-mgs; mount -t lustre   		                   /dev/vda5 /mnt/lustre-mgs
eagle-38vm3: mount.lustre: according to /etc/mtab /dev/vda5 is already mounted on /mnt/lustre-mgs
Start of /dev/vda5 on mgs failed 17

Maloo report: https://testing.hpdd.intel.com/test_sets/c5f6aa86-591c-11e6-b5b1-5254006e85c2

Issue Links

• is related to: LU-8552 Problems of testing with a separated MGS in conf-sanity.sh:
• is related to: LU-8688 All Lustre test suites should run/PASS with separate MDS and MGS

Comments

[Peter Jones]

Landed for 2.9

[Gerrit Updater]

Oleg Drokin ([e-mail]) merged in patch http://review.whamcloud.com/21653/
Subject: LU-8474 tests: stop MGS before setup_noconfig in conf-sanity.sh
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 5bf53789ffbff195e8f06266111fac095301519b

[Gerrit Updater]

Jian Yu ([e-mail]) uploaded a new patch: http://review.whamcloud.com/21653
Subject: LU-8474 tests: stop MGS before setup_noconfig in conf-sanity.sh
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 9eedbb7f03ad891ac6ad4d43296d2bccdc92e4d1