[LU-16683] sanity-sec test_61: timeout

• Status: Resolved
• Project: Lustre
• Affects Version/s: Lustre 2.16.0
• Fix Version/s: Lustre 2.16.0
• Type: Bug
• Priority: Minor
• Reporter: Maloo
• Assignee: Sebastien Buisson
• Resolution: Fixed
• Severity: 3

Description

This issue was created by maloo for S Buisson <[e-mail]>

This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/e9a6e399-5436-4f4f-b3ce-037927b221ad

test_61 failed with the following error:

Timeout occurred after 294 minutes, last suite running was sanity-sec

Test session details:
clients: https://build.whamcloud.com/job/lustre-reviews/93375 - 4.18.0-348.7.1.el8_5.x86_64
servers: https://build.whamcloud.com/job/lustre-reviews/93375 - 4.18.0-348.23.1.el8_lustre.x86_64

The timeout occurs when trying to mount the client, once it has been added to nodemap 'c0'. But read-only is not enforced yet.
The problem is because of SSK in place, the key being used is not the right one.

VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
sanity-sec test_61 - Timeout occurred after 294 minutes, last suite running was sanity-sec

Comments

[Gerrit Updater]

"Sebastien Buisson <[e-mail]>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/50476
Subject: LU-16683 tests: fix sanity-sec test_61 for SSK
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 2f1c1d9bc142b9b79b420bca778430f40f8bc403

[Gerrit Updater]

"Andreas Dilger <[e-mail]>" merged in patch https://review.whamcloud.com/c/fs/lustre-release/+/50476/
Subject: LU-16683 tests: fix sanity-sec test_61 for SSK
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 05e5cb0b0c07e15f51ce4e8fa26e12c178ab404a

[Andreas Dilger]

landed for 2.16.0