Details
-
Bug
-
Resolution: Fixed
-
Major
-
None
-
None
-
3
-
9223372036854775807
Description
MGC started on MGS uses always single peer @lo no matter what other services are running on the same node. That leads to situation when MGS is failed over then no services on primary node are able to reach it.
Solution is to account all 'mgsnode' parameters parsed in lustre_start_mgc() from any user of MGC and adding them to MGC import
Merged for 2.17