-
Bug
-
Resolution: Not a Bug
-
Normal
-
None
-
4.20.0
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
Yes
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
If a new MC is created while a MOSB is building an image, this MOSB should be removed and a new MOSB should be created to build the new image including the new MC
Version-Release number of selected component (if applicable):
IPI on AWS oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.20.0-0.nightly-2025-06-27-040027 True False 6h41m Cluster version is 4.20.0-0.nightly-2025-06-27-040027
How reproducible:
Always
Steps to Reproduce:
1. Enable Image Mode createing a MOSC 2. When the MOSB resource starts building the image create a MC
Actual results:
The os-builder pod reports this failure 2025-06-27T15:05:59.659487694Z I0627 15:05:59.659453 1 reconciler.go:1114] Updating MachineConfigPool "worker" 2025-06-27T15:05:59.659487694Z I0627 15:05:59.659470 1 reconciler.go:376] Rendered config for pool worker changed from rendered-worker-55c9b4e5fab5c47c17d76fc81f9170d7 to rendered-worker-8515ab5c29e8ea71aafd77381d625303 2025-06-27T15:05:59.659518627Z I0627 15:05:59.659502 1 reconciler.go:1401] pool "worker": No new image needs to be created, reusing last MOSB 2025-06-27T15:05:59.659518627Z I0627 15:05:59.659514 1 reconciler.go:1117] Finished updating MachineConfigPool "worker" after 311.31µs 2025-06-27T15:05:59.659541899Z I0627 15:05:59.659527 1 wrappedqueue.go:249] Error executing "<kind: \"MachineConfigPool\", name: \"worker\", func: \"(*OSBuildController).updateMachineConfigPool\">" in queue machineosbuilder: Updatin g MachineConfigPool "worker" failed: could not create or reuse existing MachineOSBuild for MachineConfigPool "worker" change: failed to look up MachineOSBuild for pull-spec "": required pullspec empty 2025-06-27T15:05:59.659565414Z E0627 15:05:59.659552 1 wrappedqueue.go:250] " And the current MOSB is not properly handled.
Expected results:
When a MOSB is building an image and a new MC is created, the current MOSB should be deleted and a new MOSB should be created containing the new MC The expected behaviour is fully described here: https://polarion.engineering.redhat.com/polarion/#/project/OSE/workitem?id=OCP-77576
Additional info: