[LU-13002] sanity-lnet stops all test suites from running

• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.14.0
• Affects Version/s: Lustre 2.13.0, Lustre 2.14.0
• Severity: 3
• Assignee: James Nunez (Inactive)
• Reporter: James Nunez (Inactive)

Description

sanity-lnet has some issues cleaning up at the end of the test suite that put Lustre (VMs?) into a bad state and does not allow other test suites to run. Looking at a recent test session failure at https://testing.whamcloud.com/test_sessions/1ab7866a-d3b5-4a48-b22b-953a35bf950a, we can see that sanity-lnet runs to completion, but all other test suites fail with

CMD: trevis-47vm8 loop_dev=\$(losetup -j /dev/mapper/mds1_flakey | cut -d : -f 1);
			 if [[ -z \$loop_dev ]]; then
				loop_dev=\$(losetup -f);
				losetup \$loop_dev /dev/mapper/mds1_flakey || loop_dev=;
			 fi;
			 echo -n \$loop_dev
trevis-47vm8: losetup: /dev/mapper/mds1_flakey: failed to set up loop device: No such file or directory

The last thing we see in the sanity-lnet suite_log is

CMD: trevis-47vm5.trevis.whamcloud.com lsmod | grep lnet > /dev/null &&
lctl dl | grep ' ST ' || true
opening /dev/obd failed: No such file or directory
hint: the kernel modules may not be loaded
modules unloaded.