[LU-16185] sanity-lnet test_212: Discovery should have failed Created: 23/Sep/22  Updated: 04/Nov/22  Resolved: 03/Nov/22

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.12.9
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Maloo Assignee: Frank Sehr
Resolution: Fixed Votes: 0
Labels: arm

Issue Links:
Duplicate
duplicates LU-13701 sanity-lnet test_205: @@@@@@ FAIL: Sh... Resolved
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

This issue was created by maloo for Andreas Dilger <adilger@whamcloud.com>

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

 Comments   
Comment by Andreas Dilger [ 27/Oct/22 ]

Frank investigated this and it looks like this is a duplicate of LU-13701 and needs patch https://review.whamcloud.com/40036 "LU-13701 utils: fix usage of getopt_long in portals" cherry-picked back to b2_12.

Comment by Frank Sehr [ 03/Nov/22 ]

fixed with patch https://review.whamcloud.com/40036 "LU-13701 utils: fix usage of getopt_long in portals"

Comment by Frank Sehr [ 04/Nov/22 ]

As far as I can see it would affect the LNet add drop/delay rules on aarch64. Maybe I should add it? 

Comment by Andreas Dilger [ 04/Nov/22 ]

Backporting it to b2_12 is fine if you have the time, though I don't think it is a high priority.

Generated at Sat Feb 10 03:24:47 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.