[LU-15705] sanity-lnet test_103: hang in lnetctl lnet unconfigure Created: 29/Mar/22  Updated: 30/Mar/22  Resolved: 30/Mar/22

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

Type: Bug Priority: Minor
Reporter: Maloo Assignee: WC Triage
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Related
is related to LU-15616 sanity-lnet test_226: Timeout occurre... 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/36c6122e-53f2-4db2-9181-7114aa4c6081

test_103 failed with the following error:

Timeout occurred after 250 minutes, last suite running was sanity-lnet

VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
sanity-lnet test_103 - Timeout occurred after 250 minutes, last suite running was sanity-lnet

 Comments   
Comment by Andreas Dilger [ 29/Mar/22 ]

Chris, could this test failure hit by Shaun's patch also be the same as LU-15616?

Comment by Chris Horn [ 30/Mar/22 ]

Yes, it looks like a duplicate of LU-15616 to me.

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