-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.18
-
Moderate
-
None
-
MCO Sprint 264, MCO Sprint 265, MCO Sprint 267
-
3
-
False
-
Description of problem:
In OCL, while a new image is being built the MCP is reporting Updating=false.
Version-Release number of selected component (if applicable):
4.18.0-0.nightly-2024-11-14-090045
How reproducible:
Always
Steps to Reproduce:
1. Enable techpreview
2. Create a MOSC
Actual results:
A builder pod is created, a machineosbuild resource is reporting "building" status but the MCP is reporting Updating=false
Once the MCO starts applying the image to the nodes, then the MCP starts reporting Updating=true.
For example, using an infra custom pool we get this scenario
# The MOSB reports a building status
$ oc get machineosbuild
NAME PREPARED BUILDING SUCCEEDED INTERRUPTED FAILED
mosc-infra-1adf9d0871a38cfcb8a0a3242fb78269 False True False False False
# The builder pod is running
$ oc get pods
NAME READY STATUS RESTARTS AGE
build-mosc-infra-1adf9d0871a38cfcb8a0a3242fb78269 2/2 Running 0 53s
kube-rbac-proxy-crio-ip-10-0-17-74.us-east-2.compute.internal 1/1 Running 8 10h
# But the infra pool is reporting Updating=false
$ oc get mcp
NAME CONFIG UPDATED UPDATING DEGRADED MACHINECOUNT READYMACHINECOUNT UPDATEDMACHINECOUNT DEGRADEDMACHINECOUNT AGE
infra rendered-infra-8336591613a94060cb7d8a1a8319dc8e True False False 0 0 0 0 62m
master rendered-master-ae24125af2c010fe672af84ce06153d9 True False False 3 3 3 0 10h
worker rendered-worker-1c0c28ca4046a899927f4417754955c6 True False False 2 2 2 0 10h
Expected results:
The pool should report Updating=true when the a new MC is rendered and MCO starts building a new image.
Additional info:
Currently our automation for OCL relies on the MCP reporting Updating=true while the new image is being built so automation for OCL cannot be used until this issue is fixed.
