-
Bug
-
Resolution: Won't Do
-
Minor
-
None
-
4.12, 4.11.z
-
Moderate
-
Rejected
-
False
-
Description of problem:
Upgrading from 4.11.20 to 4.12 (4.12.0-0.ci-2022-12-16-055410)
Version-Release number of selected component (if applicable):
How reproducible:
N/A
Steps to Reproduce:
1. Deploy fresh 4.11.20 cluster (250 node cluster) 2. Apply load 3. Upgrade to 4.12
Actual results:
Unable to apply 4.12.0-0.ci-2022-12-16-055410: the workload openshift-machine-api/control-plane-machine-set-operator has not yet successfully rolled out
Expected results:
Successful Upgrade
Additional info:
[stack@undercloud kube-burner]$ oc get co NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE authentication 4.11.20 True False False 20h baremetal 4.12.0-0.ci-2022-12-16-055410 True False False 21h cloud-controller-manager 4.12.0-0.ci-2022-12-16-055410 True False False 21h cloud-credential 4.11.20 True False False 21h cluster-autoscaler 4.11.20 True False False 21h config-operator 4.12.0-0.ci-2022-12-16-055410 True False False 21h console 4.11.20 True False False 20h control-plane-machine-set csi-snapshot-controller 4.11.20 True False False 21h dns 4.11.20 True False False 21h etcd 4.12.0-0.ci-2022-12-16-055410 True False False 21h image-registry 4.11.20 True False False 21h ingress 4.11.20 True False False 21h insights 4.11.20 True False False 21h kube-apiserver 4.12.0-0.ci-2022-12-16-055410 True False False 21h kube-controller-manager 4.12.0-0.ci-2022-12-16-055410 True False False 21h kube-scheduler 4.12.0-0.ci-2022-12-16-055410 True False False 21h kube-storage-version-migrator 4.11.20 True False False 13h machine-api 4.12.0-0.ci-2022-12-16-055410 True False False 21h machine-approver 4.11.20 True False False 21h machine-config 4.11.20 True False False 20h marketplace 4.11.20 True False False 21h monitoring 4.11.20 True False False 20h network 4.11.20 True False False 21h node-tuning 4.11.20 True False False 21h openshift-apiserver 4.11.20 True False False 21h openshift-controller-manager 4.11.20 True False False 161m openshift-samples 4.11.20 True False False 21h operator-lifecycle-manager 4.11.20 True False False 21h operator-lifecycle-manager-catalog 4.11.20 True False False 21h operator-lifecycle-manager-packageserver 4.11.20 True False False 21h service-ca 4.11.20 True True False 21h Progressing: ... storage 4.11.20 True False False 20h
Looking at the `service-ca` we see
167m Warning Failed pod/service-ca-7bfff78f48-kcp2s Error: container has runAsNonRoot and image will run as root (pod: "service-ca-7bfff78f48-kcp2s_openshift-service-ca(765648c8-e35f-4314-9fe3-bb91cc20d1bf)", container: service-ca-controller)
