-
Bug
-
Resolution: Unresolved
-
Undefined
-
4.20
-
Quality / Stability / Reliability
-
False
-
-
3
-
None
-
None
-
None
-
None
-
MCO Sprint 274
-
1
-
In Progress
-
Release Note Not Required
-
None
-
None
-
None
-
None
-
None
Description of problem:
Based on this https://github.com/openshift/machine-config-operator/pull/4996.
After applying the (ssh/password/file) based MC on OCL enabled cluster the MCP stuck on updating state.But for OCL disabled cluster able to see the expected scenario e.g: https://github.com/openshift/machine-config-operator/pull/4996#issuecomment-2919639040
Version-Release number of selected component (if applicable):
4.20
How reproducible:
Always
Steps to Reproduce:
1. Apply MOSC
2. Wait for MOSB to be successful
3. Apply the below ssh based MC
oc create -f - << EOF apiVersion: machineconfiguration.openshift.io/v1 kind: MachineConfig metadata: labels: machineconfiguration.openshift.io/role: worker name: tc-ssh spec: config: ignition: version: 3.2.0 passwd: users: - name: core sshAuthorizedKeys: - "ssh-rsa AAAAB3N......mco_test@redhat.com" EOF machineconfig.machineconfiguration.openshift.io/tc-ssh created oc get mc NAME GENERATEDBYCONTROLLER IGNITIONVERSION AGE .... rendered-worker-883d6a3e38d7dff0569a3c807b9556ca 433fd83ae10b547a586135353bff7cf108fc8f5b 3.5.0 1s .... tc-ssh 3.2.0 6s
4. Able to see MCP is stuck in updating state
oc get mcp NAME CONFIG UPDATED UPDATING DEGRADED MACHINECOUNT READYMACHINECOUNT UPDATEDMACHINECOUNT DEGRADEDMACHINECOUNT AGE master rendered-master-7ab53ca8a07e229cd32669d6843afc35 True False False 3 3 3 0 3h44m worker rendered-worker-58886972ca1d6c575a436196ccb484e6 False True False 3 0 0 0 3h44m oc get mcp worker -o yaml - lastTransitionTime: "2025-07-07T08:36:04Z" message: 'Pool is waiting for a new OS image build to start (mosc: worker-4)' reason: "" status: "True" type: Updating
Actual results:
Expected results:
https://github.com/openshift/machine-config-operator/pull/4996#issuecomment-2919639040
Additional info:
