-
Bug
-
Resolution: Done-Errata
-
Major
-
4.16.z
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
OCP Node Sprint 269 (Blue)
-
1
-
Done
-
Bug Fix
-
-
None
-
None
-
None
-
None
Description of problem:
Cluster upgrade from 4.16 to 4.17 failed The master and worker MCPs are degraded with the below error: $ oc get mcp worker -o yaml - lastTransitionTime: '2025-02-27T13:15:20Z' message: 'Failed to render configuration for pool sbb-worker-app: could not generate rendered MachineConfig: Ignoring MC 99-sbb-worker-app-generated-containerruntime generated by older version 9e721f05c02ec0dd8d1f4d58b95462bb87748f17 (my version: 11006a412aba038bbddc5b3c1a8040ca1d9c8b47)' reason: '' status: 'True' type: RenderDegraded $ oc get mcp master -o yaml - lastTransitionTime: '2025-02-27T13:15:20Z' message: 'Failed to render configuration for pool master: could not generate rendered MachineConfig: Ignoring MC 99-master-generated-containerruntime-2 generated by older version 9e721f05c02ec0dd8d1f4d58b95462bb87748f17 (my version: 11006a412aba038bbddc5b3c1a8040ca1d9c8b47)' reason: '' status: 'True' type: RenderDegraded There is only single machiconfig present for master and worker MCP: omg get mc | grep registries 99-master-generated-registries 11006a412aba038bbddc5b3c1a8040ca1d9c8b47 3.4.0 1131d 99-worker-generated-registries 11006a412aba038bbddc5b3c1a8040ca1d9c8b47 3.4.0 1131d
Actual results:
Update stucks on machine-config CO
Expected results:
Upgrade should continue without any issue.
- depends on
-
OCPBUGS-54296 Cluster upgrade stuck due to machine-config CO in degraded state
-
- Closed
-
- is blocked by
-
OCPNODE-3119 OCPBUGS-52188 Impact: Cluster upgrade stuck due to machine-config CO in degraded state
-
- Closed
-
- is cloned by
-
OCPBUGS-54296 Cluster upgrade stuck due to machine-config CO in degraded state
-
- Closed
-
- links to
-
RHBA-2025:3798 OpenShift Container Platform 4.17.z bug fix update