[LU-8705] fix lnet-selftest to be not skipped on DNE Created: 13/Oct/16  Updated: 25/Oct/16  Resolved: 25/Oct/16

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

Type: Bug Priority: Minor
Reporter: Elena Gryaznova Assignee: Doug Oucharek (Inactive)
Resolution: Fixed Votes: 0
Labels: patch

Issue Links:
Duplicate
Related
is related to LU-4181 lnet-selftest test_smoke: lst error f... Resolved
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

LU-4181 disabled lnet_selftest.sh for DNE:

commit 9db076aabb2b337b742ae0f91ed6bbe047c67058
Author:     wang di <di.wang@intel.com>
AuthorDate: Thu Oct 31 00:01:15 2013 -0700
Commit:     Vitaly Fertman <vitaly.fertman@seagate.com>
CommitDate: Mon Sep 15 17:59:14 2014 +0400
    LU-4181 tests: disable lnet_selftest.sh for DNE.
    Disable lnet_selftest for DNE to make review pass with DNE.

LU-4181 describes different lnet-selftest failures and does not state that the reason of these failures is DNE config.

We need lnet-selftest run on Neo based clusters.
It is reasonable to remove the "skip" added by LU-4181.



 Comments   
Comment by Gerrit Updater [ 13/Oct/16 ]

Elena Gryaznova (elena.gryaznova@seagate.com) uploaded a new patch: http://review.whamcloud.com/23138
Subject: LU-8705 tests: do not skip lnet-selftest for DNE
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: eabbd0ee856b216d831062cf042ee842a939eeac

Comment by Andreas Dilger [ 13/Oct/16 ]

Yes, it should be fine to remove this exclusion. This problem was a result of lnet-selftest consuming all network bandwidth and causing the MDS nodes to go into recovery. This was later fixed to stop all Lustre services when running lnet-selftest and there shouldn't be any problem to re-enable it.

Comment by Gerrit Updater [ 25/Oct/16 ]

Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/23138/
Subject: LU-8705 tests: do not skip lnet-selftest for DNE
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: b4e0b8d4d0634e79f8c4dcf8cfa434db3a97f0be

Comment by Peter Jones [ 25/Oct/16 ]

Landed for 2.9

Generated at Sat Feb 10 02:19:51 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.