-
Bug
-
Resolution: Done-Errata
-
Normal
-
None
-
4.17.z, 4.18.z, 4.19.0
-
Moderate
-
None
-
2
-
MCO Sprint 266
-
1
-
False
-
-
Release Note Not Required
-
In Progress
This is a clone of issue OCPBUGS-48250. The following is the description of the original issue:
—
Trying to solve the root issue from this bug: https://issues.redhat.com/browse/OCPBUGS-39199?focusedId=26104570&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-26104570
To fix this, we need each of the sync functions to be able to individually clear a CO degrade that they have set earlier. Our current flow only clears a CO degrade when the all of sync functions are successful and that tends to be problematic if they happen to get stuck in one of the sync functions. We typically see this for syncRequiredMachineConfigPools, which waits until the master nodes have finished updating during an upgrade.
- blocks
-
OCPBUGS-49716 MCO CO degrades are stuck on until master pool updates complete
-
- Closed
-
- clones
-
OCPBUGS-48250 MCO CO degrades are stuck on until master pool updates complete
-
- Verified
-
- is blocked by
-
OCPBUGS-48250 MCO CO degrades are stuck on until master pool updates complete
-
- Verified
-
- is cloned by
-
OCPBUGS-49716 MCO CO degrades are stuck on until master pool updates complete
-
- Closed
-
- links to
-
RHEA-2024:6122 OpenShift Container Platform 4.18.z bug fix update