Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Assignee
Ali AlsulimanAli AlsulimanReporter
Ali AlsulimanAli AlsulimanIs this a Regression?
YesTriage
UntriagedStory Points
1Sprint
NonePriority
CriticalInstabug
Open Instabug
Details
Details
Assignee
Ali Alsuliman
Ali AlsulimanReporter
Ali Alsuliman
Ali AlsulimanIs this a Regression?
Yes
Triage
Untriaged
Story Points
1
Sprint
None
Priority
Instabug
Open Instabug
PagerDuty
PagerDuty
PagerDuty
Sentry
Sentry
Sentry
Zendesk Support
Zendesk Support
Zendesk Support
Created March 16, 2022 at 8:55 PM
Updated June 14, 2023 at 9:56 PM
Resolved March 17, 2022 at 6:58 PM
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.