I'm going to mark this as a blocker+. This is a regression in 4.11 that causes a potential panic in the MCO (machine-config-daemon pod specifically) if the user attempts to ssh into nodes, and can be an upgrade blocking issue. The fix is very simple and safe, so I think it's worth merging into 4.11.0
Issue with MachineConfigPool is not seen on 4.11.0-rc.2 build [root@rdr-ci-ocp-upi-a7bf-tor01-bastion-0 ~]# oc version Client Version: 4.11.0-rc.2 Kustomize Version: v4.5.4 Server Version: 4.11.0-rc.2 Kubernetes Version: v1.24.0+9546431 [root@rdr-ci-ocp-upi-a7bf-tor01-bastion-0 ~]# oc get mcp NAME CONFIG UPDATED UPDATING DEGRADED MACHINECOUNT READYMACHINECOUNT UPDATEDMACHINECOUNT DEGRADEDMACHINECOUNT AGE master rendered-master-44d47954f24666349149b34be4fdcbf9 True False False 3 3 3 0 55m worker rendered-worker-495bb191d4d14a21b89733276315bf3b True False False 2 2 2 0 55m [root@rdr-ci-ocp-upi-a7bf-tor01-bastion-0 ~]# oc get pod -n openshift-machine-config-operator -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES machine-config-controller-dbcc464ff-n7fjv 2/2 Running 0 68m 10.128.0.10 tor01-master-1.rdr-ci-ocp-upi-a7bf.redhat.com <none> <none> machine-config-daemon-57wbb 2/2 Running 0 51m 193.168.200.80 tor01-worker-0.rdr-ci-ocp-upi-a7bf.redhat.com <none> <none> machine-config-daemon-bm22f 2/2 Running 0 69m 193.168.200.51 tor01-master-2.rdr-ci-ocp-upi-a7bf.redhat.com <none> <none> machine-config-daemon-fwt7b 2/2 Running 0 64m 193.168.200.221 tor01-master-0.rdr-ci-ocp-upi-a7bf.redhat.com <none> <none> machine-config-daemon-hhx2b 2/2 Running 0 50m 193.168.200.230 tor01-worker-1.rdr-ci-ocp-upi-a7bf.redhat.com <none> <none> machine-config-daemon-v678k 2/2 Running 0 69m 193.168.200.3 tor01-master-1.rdr-ci-ocp-upi-a7bf.redhat.com <none> <none> machine-config-operator-86c57dd94c-cmnwb 1/1 Running 0 73m 10.129.0.2 tor01-master-2.rdr-ci-ocp-upi-a7bf.redhat.com <none> <none> machine-config-server-jmm6d 1/1 Running 0 64m 193.168.200.221 tor01-master-0.rdr-ci-ocp-upi-a7bf.redhat.com <none> <none> machine-config-server-lxkps 1/1 Running 0 68m 193.168.200.3 tor01-master-1.rdr-ci-ocp-upi-a7bf.redhat.com <none> <none> machine-config-server-xhqdd 1/1 Running 0 68m 193.168.200.51 tor01-master-2.rdr-ci-ocp-upi-a7bf.redhat.com <none> <none> [root@rdr-ci-ocp-upi-a7bf-tor01-bastion-0 ~]# oc get pods -A | grep -v "Running\|Completed" NAMESPACE NAME READY STATUS RESTARTS AGE
move this bz to VERIFIED
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:5069