Verified Result Scale worker nodes to 6 nodes, then upgrade OCP from 4.11 to 4.12, no BZ reproduced. [ocpadmin@ec2-18-217-45-133 ~]$ oc project openshift-cluster-node-tuning-operator Now using project "openshift-cluster-node-tuning-operator" on server "https://api.liqcui-oc411n1.qe.devcluster.openshift.com:6443". [ocpadmin@ec2-18-217-45-133 ~]$ oc get pods NAME READY STATUS RESTARTS AGE cluster-node-tuning-operator-5c4b588b5d-9tqbg 1/1 Running 1 43m tuned-9qw4t 1/1 Running 1 37m tuned-chshb 1/1 Running 1 37m tuned-d4c4h 1/1 Running 1 37m tuned-dc8rf 1/1 Running 1 37m tuned-f6w9j 1/1 Running 1 37m tuned-g6zs9 1/1 Running 1 37m tuned-ktcw2 1/1 Running 1 37m [ocpadmin@ec2-18-217-45-133 ~]$ oc get tuned NAME AGE default 174m rendered 174m [ocpadmin@ec2-18-217-45-133 ~]$ oc get profile NAME TUNED APPLIED DEGRADED AGE ip-10-0-135-152.us-east-2.compute.internal openshift-control-plane True False 15m ip-10-0-141-134.us-east-2.compute.internal openshift-node True False 15m ip-10-0-171-8.us-east-2.compute.internal openshift-node True False 55m ip-10-0-175-205.us-east-2.compute.internal openshift-node True False 55m ip-10-0-182-243.us-east-2.compute.internal openshift-node True False 55m ip-10-0-182-26.us-east-2.compute.internal openshift-node True False 55m ip-10-0-183-241.us-east-2.compute.internal openshift-node True False 55m [ocpadmin@ec2-18-217-45-133 ~]$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.12.0-0.nightly-2022-08-12-053438 True False 16m Cluster version is 4.12.0-0.nightly-2022-08-12-053438 [ocpadmin@ec2-18-217-45-133 ~]$
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 (Moderate: OpenShift Container Platform 4.11.1 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:6103