Details
-
Bug
-
Resolution: Fixed
-
Critical
-
7.0.4
-
Untriaged
-
1
-
Yes
-
CX Sprint 284
Description
During upgrading nodes, a node could get into a state where the monitor for the cluster compatibility is not started because the coordinator on the node is not started. If the monitor for the cluster compatibility is not started, the node won't detect that the cluster compatibility has changed and act on it.
The attached logs show that the node could not finish booting and registering with the CC as it was still running an older version than the CC, and therefore, the coordinator was not started.
Attachments
Issue Links
- is a backport of
-
MB-51314 [CX] Node is not upgraded and stuck trying to register with CC
-
- Closed
-