-
Bug
-
Resolution: Done
-
Undefined
-
None
-
premerge, 4.16
-
Important
-
None
-
Proposed
-
False
-
Description of problem:
When we enable techpreview and we create a MachineOsConfig resource for the worker pool, the controller pod and the os-builder pods panic.
Version-Release number of selected component (if applicable):
pre-merge https://github.com/openshift/machine-config-operator/pull/4327
How reproducible:
Always
Steps to Reproduce:
1. enable techpreview oc patch featuregate cluster --type=merge -p '{"spec":{"featureSet": "TechPreviewNoUpgrade"}}' 2. Create a MachineOsConfig resource for the worker pool oc create -f - << EOF apiVersion: machineconfiguration.openshift.io/v1alpha1 kind: MachineOSConfig metadata: name: worker spec: machineConfigPool: name: worker buildInputs: imageBuilder: imageBuilderType: PodImageBuilder 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
Actual results:
The build pod is triggered, and once it finishes the os-builder pod and the controller pod panic
Expected results:
No pod should panic
Additional info:
- relates to
-
MCO-665 On-Cluster Layering Tech Preview
- Closed