[LU-7682] Interop 2.7.1<->master - sanity-benchmark: no subtests ran

• Type: Bug
• Resolution: Cannot Reproduce
• Priority: Minor
• Affects Version/s: Lustre 2.8.0, Lustre 2.9.0
• Environment: Interop: Server: master, build# 3303, RHEL 7; Client: 2.7.1, b2_7_fe/34; Also impacts master patch testing in autotest
• Severity: 3
• Assignee: Saurabh Tandan (Inactive)
• Reporter: Maloo

Description

This issue was created by maloo for Saurabh Tandan <[e-mail]>
sanity-benchmark failed with the following issue in suite_log:

Setup mgs, mdt, osts
CMD: shadow-35vm3 mkdir -p /mnt/mds1
CMD: shadow-35vm3 test -b /dev/lvm-Role_MDS/P1
Starting mds1:   /dev/lvm-Role_MDS/P1 /mnt/mds1
CMD: shadow-35vm3 mkdir -p /mnt/mds1; mount -t lustre   		                   /dev/lvm-Role_MDS/P1 /mnt/mds1
shadow-35vm3: mount.lustre: according to /etc/mtab /dev/mapper/lvm--Role_MDS-P1 is already mounted on /mnt/mds1

This issue has been seen around 18 times in past 30 days.

This issue relates to the following test suite run: https://testing.hpdd.intel.com/test_sets/607eb636-bac4-11e5-9137-5254006e85c2.

Might be related to LU-6248

Issue Links

• is related to: LU-6016 sanity-lfsck test_20a: FAIL: (1) Fail to start MDS!

Comments

[James Nunez (Inactive)]

We see this happen frequently in master patch testing, meaning in testing other than interop, where a test suite fails and then the next test suite does not run any tests because a MDT is already mounted.

In the examples below, sanity-sec, insanity, replay-ost-single, ost-pools, and sanity-hsm fail due to the mdt being mounted when the test suite starts running:

2016-01-26 - https://testing.hpdd.intel.com/test_sessions/055b35b4-c46e-11e5-a651-5254006e85c2
2016-02-17 - https://testing.hpdd.intel.com/test_sessions/fd51ce20-d546-11e5-9cc2-5254006e85c2
2016-02-21 - https://testing.hpdd.intel.com/test_sessions/a9d0887c-d8de-11e5-b4e5-5254006e85c2