-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.20
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
While executing test case "OCP-73631 - [MCO][MCO-838] Pinned images garbage collection" in a cluster with Image Mode enabled, the MCP got stuck and the MCC started reporting this error: I0704 10:38:10.285922 1 node_controller.go:1073] Requeueing layered pool worker: Image built successfully, pullspec: quay.io/mcoqe/layering@sha256:0e4c4b0c49cdc4d98308a289bf01b31bbca145e2009ddf28d1799ada3b4a41d5, but MachineOSConfig "mosc-worker" has not updated yet
Version-Release number of selected component (if applicable):
IPI on AWS version 4.20.0-0.nightly-2025-07-04-033329
How reproducible:
Cannot reproduce
Steps to Reproduce:
Cannot reproduce
Actual results:
The MCP is stuck in this status $ oc get mcp NAME CONFIG UPDATED UPDATING DEGRADED MACHINECOUNT READYMACHINECOUNT UPDATEDMACHINECOUNT DEGRADEDMACHINECOUNT AGE master rendered-master-ef318bd14dcd1f3cd2e4da03a4ce9031 True False False 3 3 3 0 3h33m worker rendered-worker-428cbd36dc2475150eb6cad890967e5a False True False 2 0 0 0 3h33m
Expected results:
MCP should not get stuck and the configurations should be properly applied using Image Mode.
Additional info: