Details
-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
3
-
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.
Attachments
Issue Links
- is related to
-
LU-17379 try MGS NIDs more quickly at initial mount
- Resolved