-
Bug
-
Resolution: Done-Errata
-
Normal
-
None
-
4.16.0
-
No
-
8
-
MCO Sprint 259
-
1
-
False
-
-
N/A
-
Release Note Not Required
-
Done
This is a clone of issue OCPBUGS-32812. The following is the description of the original issue:
—
Description of problem:
When the image from a build is rolling out on the nodes, the update progress on the node is not displaying correctly.
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Enable OCL functionality 2. Opt the pool in by MachineOSConfig 3. Wait for the image to build and roll out 4. Track mcp update status by oc get mcp
Actual results:
The MCP start with O ready pool. While there are 1-2 pools got updated already, the count still remains 0. The count jump to 3 when all the pools are ready.
Expected results:
The update progress should be reflected in the mcp status correctly.
Additional info:
- blocks
-
OCPBUGS-41806 When newly built images rolled out, the update progress is not displaying correctly (went 0 --> 3)
- Closed
- clones
-
OCPBUGS-32812 When newly built images rolled out, the update progress is not displaying correctly (went 0 --> 3)
- Verified
- is blocked by
-
OCPBUGS-32812 When newly built images rolled out, the update progress is not displaying correctly (went 0 --> 3)
- Verified
- is cloned by
-
OCPBUGS-41806 When newly built images rolled out, the update progress is not displaying correctly (went 0 --> 3)
- Closed
- links to
-
RHEA-2024:3718 OpenShift Container Platform 4.17.z bug fix update