[LU-16185] sanity-lnet test_212: Discovery should have failed

• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Affects Version/s: Lustre 2.12.9
• Labels: arm
• Severity: 3
• Assignee: Frank Sehr (Inactive)
• Reporter: Maloo

Description

This issue was created by maloo for Andreas Dilger <[e-mail]>

This issue relates to the following test suite run:
https://testing.whamcloud.com/test_sets/cbe19d9e-7c85-41e5-96cb-e56f1601e43c

test_212 failed with the following error:

discover:
    - primary nid: 10.240.27.140@tcp
      Multi-Rail: True
      peer ni:
        - nid: 10.240.27.140@tcp
Fail local discover ping to set LNET_PEER_REDISCOVER flag
error: net_drop_add: option 'local_error' unrecognized
/usr/sbin/lnetctl discover --force 10.240.26.0@tcp
discover:
    - primary nid: 10.240.26.0@tcp
      Multi-Rail: True
      peer ni:
        - nid: 10.240.26.0@tcp
 sanity-lnet test_212: @@@@@@ FAIL: Discovery should have failed 

It looks like this is failing 100% on 2.12.x branches for aarch64 or ppcle64, but not x86 clients.

VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
sanity-lnet test_212 - Discovery should have failed

Issue Links

• duplicates: LU-13701 sanity-lnet test_205: @@@@@@ FAIL: Should have failed