-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.18
-
Moderate
-
No
-
2
-
MCO Sprint 266, MCO Sprint 267
-
2
-
False
-
-
Release Note Not Required
-
In Progress
Description of problem:
When we upgrade an OCL cluster from 4.18 -> 4.18, and we configure a machineset so that its base cloud Image is automatically updated in the upgrade, the machine-config CO may become degraded with this message:
- lastTransitionTime: "2025-01-24T19:58:23Z"
message: 'Unable to apply 4.18.0-0.nightly-2025-01-24-014549: bootimage update
failed: 1 Degraded MAPI MachineSets | 0 Degraded CAPI MachineSets | 0 CAPI MachineDeployments
| Error(s): error syncing MAPI MachineSet cloned-tc-70813-label: timed out waiting
for coreos-bootimages config map: mismatch between MCO hash version stored in
configmap and current MCO version; sync will exit to wait for the MCO upgrade
to complete'
reason: MachineConfigurationFailed
status: "True"
type: Degraded
Link to the prow execution: https://qe-private-deck-ci.apps.ci.l2s4.p1.openshiftapps.com/view/gs/qe-private-deck/logs/periodic-ci-openshift-openshift-tests-private-release-4.18-amd64-nightly-4.18-upgrade-from-stable-4.18-aws-ipi-ocl-fips-f60/1882788481910968320
Version-Release number of selected component (if applicable):
Upgrading from 4.18.0-rc.6 to 4.18.0-0.nightly-2025-01-24-014549
How reproducible:
Rarely
Steps to Reproduce:
1. install 4.18.0-rc.6
2. Clone an existing machineset
3. Configure the new machineset so that its base cloud image is updated automatically in the upgraded. Use a label configuration, so that only this machineset is updated.
4. Upgrade to 4.18.0-0.nightly-2025-01-24-014549
Actual results:
The machine-config CO is degraded with this message:
- lastTransitionTime: "2025-01-24T19:58:23Z"
message: 'Unable to apply 4.18.0-0.nightly-2025-01-24-014549: bootimage update
failed: 1 Degraded MAPI MachineSets | 0 Degraded CAPI MachineSets | 0 CAPI MachineDeployments
| Error(s): error syncing MAPI MachineSet cloned-tc-70813-label: timed out waiting
for coreos-bootimages config map: mismatch between MCO hash version stored in
configmap and current MCO version; sync will exit to wait for the MCO upgrade
to complete'
reason: MachineConfigurationFailed
status: "True"
type: Degraded
Expected results:
Additional info:
It looks like the coreos-bootimages configma was never updated with the new MCOVersionHash
It may not be related to OCL at all.
