[LU-3352] conf-sanity test_73: failover nids haven't changed

• Type: Bug
• Resolution: Fixed
• Priority: Blocker
• Fix Version/s: Lustre 2.4.1, Lustre 2.5.0
• Affects Version/s: Lustre 2.4.0
• Severity: 3
• Assignee: Emoly Liu
• Reporter: Maloo

Description

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

This issue relates to the following test suite run: http://maloo.whamcloud.com/test_sets/e5d0ffde-bd82-11e2-a548-52540035b04c.

The sub-test test_73 failed with the following error in the test output:

failover nids haven't changed

Info required for matching: conf-sanity 73

Issue Links

• is related to: LU-3006 failover nids added after format don't propogate to clients
• is related to: LU-3244 Test failure on test suite conf-sanity, subtest test_73: failure to start ost

Comments

[Jian Yu]

Patch was cherry-picked to Lustre b2_4 branch.

[Jian Yu]

http://review.whamcloud.com/6550

The patch also needs to be cherry-picked to Lustre b2_4 branch to resolve interop failure with old servers.

[Emoly Liu]

patch landed

[Jodi Levi (Inactive)]

Can this ticket be closed now that the patch has landed to Master?

[Keith Mannthey (Inactive)]

The patch for test_73 is Acked and waiting for Gatekeeper.

[Bob Glossman (Inactive)]

another instance:
https://maloo.whamcloud.com/test_sets/ce5f8ca0-d7bb-11e2-b179-52540035b04c

[Emoly Liu]

OK, I will check if there are other improper NID settings in out test scripts.

[Keith Mannthey (Inactive)]

Should we remove all of @tpc from the test scripts?

[Emoly Liu]

http://review.whamcloud.com/6550

[Emoly Liu]

This problem is probably caused by the script

do_facet ost1 "$TUNEFS --failnode=1.2.3.4@tcp $(ostdevname 1)"

removing "@tcp" should work on IB network.