[LU-13701] sanity-lnet test_205: @@@@@@ FAIL: Should have failed Created: 22/Jun/20  Updated: 07/Nov/22  Resolved: 12/Oct/20

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

Type: Bug Priority: Minor
Reporter: Maloo Assignee: Serguei Smirnov
Resolution: Fixed Votes: 0
Labels: arm

Issue Links:
Duplicate
is duplicated by LU-16185 sanity-lnet test_212: Discovery shoul... Resolved
Related
is related to LU-13704 sanity-lnet test_204: local_interrupt... Resolved
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

This issue was created by maloo for wangshilong <wshilong@ddn.com>

This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/e251a96e-a78a-4afe-b5dd-7fca780a76cf

test_205 failed with the following error:

Should have failed

<<Please provide additional information about the failure here>>

VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
sanity-lnet test_205 - Should have failed



 Comments   
Comment by Emoly Liu [ 23/Jun/20 ]

+1 on master:
https://testing.whamcloud.com/test_sets/88ec3640-5fdc-466e-8a5e-3d35ac7b5ea7

Comment by Gerrit Updater [ 23/Jun/20 ]

James Nunez (jnunez@whamcloud.com) uploaded a new patch: https://review.whamcloud.com/39155
Subject: LU-13701 tests: stop running sanity-lnet 205
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 7d996ad38aac5ac5f4f32d598f6816229cc9300a

Comment by Andreas Dilger [ 24/Jun/20 ]

Do we know when these failures started? Are they because of newly landed subtests, or possibly new lnet changes or a kernel update?

Comment by Gerrit Updater [ 26/Jun/20 ]

Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/39155/
Subject: LU-13701 tests: stop running sanity-lnet tests
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 32155957a7de12a2324dc184350c737f8c1650d1

Comment by James Nunez (Inactive) [ 26/Jun/20 ]

The patch that landed adds sanity-lnet tests 204, 205, 206, 207 and 208 to the ALWAYS_EXCEPT list and is not a fix for this issue.

This ticket should remain open until we understand and fix this issue.

Comment by Chris Horn [ 15/Sep/20 ]

As noted in LU-13704, there seems to be some problem with the lctl net_drop_add command:

error: net_drop_add: option 'local_error' unrecognized
error: net_drop_add: option 'local_error' unrecognized
Comment by Gerrit Updater [ 25/Sep/20 ]

Serguei Smirnov (ssmirnov@whamcloud.com) uploaded a new patch: https://review.whamcloud.com/40036
Subject: LU-13701 utils: fix usage of getopt_long in portals
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: bc69b387112a8cfb03a313a4e82028ef3433a63e

Comment by Gerrit Updater [ 12/Oct/20 ]

Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/40036/
Subject: LU-13701 utils: fix usage of getopt_long in portals
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 404bb62da49ca33bdc6e287a12e69d086a1fa4c2

Comment by Peter Jones [ 12/Oct/20 ]

Landed for 2.14

Comment by Gerrit Updater [ 07/Nov/22 ]

"Frank Sehr <fsehr@whamcloud.com>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/49063
Subject: LU-13701 utils: fix usage of getopt_long in portals
Project: fs/lustre-release
Branch: b2_12
Current Patch Set: 1
Commit: 7783a78d27ffebad9e58241655b63a21cf21db60

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