[LU-17331] conf-sanity test_30b: FAIL: check lustre-OST0000.failover.node failed!

• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.16.0
• Severity: 3
• Assignee: Andreas Dilger
• Reporter: Maloo

Description

This issue was created by maloo for Minh Diep <[e-mail]>

This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/a97ddad2-140b-4c93-9521-e5998de29b6f

test_30b failed with the following error:

check lustre-OST0000.failover.node failed!

Test session details:
clients: https://build.whamcloud.com/job/lustre-b2_15/77 - 5.14.0-284.30.1.el9_2.x86_64
servers: https://build.whamcloud.com/job/lustre-b2_15/77 - 4.18.0-477.15.1.el8_lustre.x86_64

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

VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
conf-sanity test_30b - check lustre-OST0000.failover.node failed!

Issue Links

• is related to: LU-18013 conf-sanity test_30b fails with large NIDs
• is related to: LU-18356 test-framework to fetch except list from server for interop testing

Comments

[Andreas Dilger]

It looks like this subtest is still failing with b2_15 clients during interop testing.

[Peter Jones]

Merged for 2.16

[Gerrit Updater]

"Oleg Drokin <[e-mail]>" merged in patch https://review.whamcloud.com/c/fs/lustre-release/+/55890/
Subject: LU-17331 tests: fix conf-sanity/30b fake NID generation
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 0f1f5c8dfd43dbdfffbf4057d927ee5ba555c7af

[Andreas Dilger]

It looks like this subtest is randomly failing in the case where the client NID = OST NID + 20, which the test is using as a "fake NID".

[Gerrit Updater]

"Andreas Dilger <[e-mail]>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/55890
Subject: LU-17331 tests: fix conf-sanity/30b fake NID generation
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 7319d38d772b385d75cd4841bb3da792aa714d45