[LU-17357] Client can use incorrect sec flavor when MGT is relocated

• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.16.0
• Labels: gss patch sec
• Severity: 3
• Assignee: Sebastien Buisson
• Reporter: Sebastien Buisson

Description

In case the MGT is moved to a secondary location, it might take time for the client to connect and retrieve the config logs. Under some circumstances, we can end up in a situation where the client tries to connect to the other targets (MDT, OST) before having retrieved the sptlrpc logs. As a consequence, the client does not use the required security flavor, and mount fails.

Issue Links

• is related to: LU-17379 try MGS NIDs more quickly at initial mount

Comments

[Alex Zhuravlev]

having this patch applied MDSCOUNT=2 OSTCOUNT=2 ONLY=19 bash sanity-scrub.sh:
PASS 19 (393s)

with the patch reverted:
PASS 19 (150s)

[Peter Jones]

Landed for 2.16

[Gerrit Updater]

"Oleg Drokin <[e-mail]>" merged in patch https://review.whamcloud.com/c/fs/lustre-release/+/53423/
Subject: LU-17357 mgc: wait for sptlrpc config log
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 4a3e428361a03b4bc777eddd466ba1ff8b72b51e

[Gerrit Updater]

"Sebastien Buisson <[e-mail]>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/53423
Subject: LU-17357 mgc: wait for sptlrpc config log
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 29f7521945f3fc7e6dd47415b8cb2dada33fc3b4