-
Bug
-
Resolution: Unresolved
-
Major
-
4.20
-
None
-
Quality / Stability / Reliability
-
False
-
-
2
-
None
-
None
-
None
-
Proposed
-
MCO Sprint 275
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
- Deployed the 4.20.0-0.nightly-2025-08-10-050301 cluster. - when I try to deploy the MOSC the MOSB is not triggred or changes like cm, job, secret, build pod not created. - Tried to deploy MC the MCP is getting updated and able to see changes on node.(non-OCL)
Version-Release number of selected component (if applicable):
4.20
How reproducible:
Always
Steps to Reproduce:
1.Apply MOSC on newly created cluster 2.Able to see no changes in MCP status or anything related to OCL
Actual results:
$ oc get po -n openshift-machine-config-namespace ... machine-config-nodes-crd-cleanup-29248202-xtdtj 0/1 Completed 0 52m $ Apply MOSC oc create -f - << EOF apiVersion: machineconfiguration.openshift.io/v1 kind: MachineOSConfig metadata: name: worker-4 spec: machineConfigPool: name: worker imageBuilder: imageBuilderType: Job baseImagePullSecret: name: $(oc get secret -n openshift-config pull-secret -o json | jq "del(.metadata.namespace, .metadata.creationTimestamp, .metadata.resourceVersion, .metadata.uid, .metadata.name)" | jq '.metadata.name="pull-copy"' | oc -n openshift-machine-config-operator create -f - &> /dev/null; echo -n "pull-copy") renderedImagePushSecret: name: $(oc get -n openshift-machine-config-operator sa builder -ojsonpath='{.secrets[0].name}') renderedImagePushSpec: "image-registry.openshift-image-registry.svc:5000/openshift-machine-config-operator/ocb-image:latest" EOF $ oc get machineosbuilds No resources found $ oc get job NAME STATUS COMPLETIONS DURATION AGE machine-config-nodes-crd-cleanup-29248202 Complete 1/1 2m13s 147m
Expected results:
Able to have MOSC image deployed on node.
Additional info:
must-gather: https://drive.google.com/drive/folders/11G_ECKrVd7Lwm-YPo5gJ1EsORc3EVx-P?usp=sharing