[LU-15024] sanity-sec test_31: timeout on lnetctl lnet unconfigure

• Type: Bug
• Resolution: Unresolved
• Priority: Minor
• Severity: 3
• Assignee: WC Triage
• Reporter: Maloo

Description

This issue was created by maloo for S Buisson <[e-mail]>

This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/b6f0a188-3fc3-41fb-88f8-3984ea402e44

test_31 failed with the following error:

Timeout occurred after 224 mins, last suite running was sanity-sec

This timeout occurs when trying to unconfigure LNet after the failed attempt to mount the client with -o network=<NETTYPE>999 option (it fails as expected because of LNet Dynamic Discovery):

Starting client: onyx-22vm1.onyx.whamcloud.com:  -o user_xattr,flock,skpath=/tmp/test-framework-keys,network=tcp999 10.2.4.24@tcp999:/lustre /mnt/lustre
CMD: onyx-22vm1.onyx.whamcloud.com mkdir -p /mnt/lustre
CMD: onyx-22vm1.onyx.whamcloud.com mount -t lustre -o user_xattr,flock,skpath=/tmp/test-framework-keys,network=tcp999 10.2.4.24@tcp999:/lustre /mnt/lustre
mount.lustre: mount 10.2.4.24@tcp999:/lustre at /mnt/lustre failed: Invalid argument
This may have multiple causes.
Is 'lustre' the correct filesystem name?
Are the mount options correct?
Check the syslog for more info.
unconfigure:
    - lnet:
          errno: -16
          descr: "LNet unconfigure error: Device or resource busy"

VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
sanity-sec test_31 - Timeout occurred after 224 mins, last suite running was sanity-sec