[LU-15321] sanity: test_427 TIMEOUT

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

Description

This issue was created by maloo for Sergey Cheremencev <[e-mail]>

This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/ed1a7781-48c4-49d7-967f-61bb0390cb04

Error: 'Timeout occurred after 360 mins, last suite running was sanity'

== sanity test 427: Failed DNE2 update request shouldn't corrupt updatelog ========================================================== 17:05:47 (1638551147)
...
Failing mds2 on onyx-25vm8
CMD: onyx-25vm8 grep -c /mnt/lustre-mds2' ' /proc/mounts || true
Stopping /mnt/lustre-mds2 (opts:) on onyx-25vm8
CMD: onyx-25vm8 umount -d /mnt/lustre-mds2
CMD: onyx-25vm8 lsmod | grep lnet > /dev/null &&
lctl dl | grep ' ST ' || true
reboot facets: mds2
Failover mds2 to onyx-25vm8
CMD: onyx-25vm8 hostname

Console messages from onyx-25vm8 (MDS2, MDS4):

[18037.196528] LustreError: 137-5: lustre-MDT0001_UUID: not available for connect from 10.240.22.106@tcp (no target). If you are running an HA pair check that the target is mounted on the other server.
[18037.199692] LustreError: Skipped 13 previous similar messages
[18038.235021] LustreError: 137-5: lustre-MDT0001_UUID: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server.
[18039.439966] LustreError: 137-5: lustre-MDT0001_UUID: not available for connect from 10.240.26.10@tcp (no target). If you are running an HA pair check that the target is mounted on the other server.
[18039.444998] LustreError: Skipped 8 previous similar messages
...
[21467.476476] LustreError: 137-5: lustre-MDT0001_UUID: not available for connect from 10.240.22.106@tcp (no target). If you are running an HA pair check that the target is mounted on the other server.
[21467.479898] LustreError: Skipped 1521 previous similar messages

Issue Links

• duplicates: LU-15320 sanity-quota: test_59 TIMEOUT