[LU-17357] Client can use incorrect sec flavor when MGT is relocated Created: 12/Dec/23 Updated: 23/Jan/24 |
|
| Status: | Open |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Sebastien Buisson | Assignee: | Sebastien Buisson |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | gss, patch, sec | ||
| Issue Links: |
|
||||||||
| Severity: | 3 | ||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||
| 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. |
| Comments |
| Comment by Gerrit Updater [ 12/Dec/23 ] |
|
"Sebastien Buisson <sbuisson@ddn.com>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/53423 |