*** Bug 2083389 has been marked as a duplicate of this bug. ***
Verified on version below. Creating new sriovnetworknodepolicy before last policy sync up succeed, worker nodes can be ready successfully. # oc version Client Version: 4.11.0-0.nightly-2022-06-11-054027 Kustomize Version: v4.5.4 Server Version: 4.8.49 Kubernetes Version: v1.21.11+31d53a1 [root@dell-per740-36 yingwang]# [root@dell-per740-36 yingwang]# [root@dell-per740-36 yingwang]# oc get csv NAME DISPLAY VERSION REPLACES PHASE sriov-network-operator.4.8.0-202208310016 SR-IOV Network Operator 4.8.0-202208310016 Succeeded # oc get sriovnetworknodepolicies.sriovnetwork.openshift.io NAME AGE default 47m mlx277dpdkpolicy 26m mlx277netpolicy 25m # oc get nodes NAME STATUS ROLES AGE VERSION dell-per740-13.rhts.eng.pek2.redhat.com Ready master 3h31m v1.21.11+31d53a1 dell-per740-14.rhts.eng.pek2.redhat.com Ready worker 155m v1.21.11+31d53a1 dell-per740-31.rhts.eng.pek2.redhat.com Ready master 3h32m v1.21.11+31d53a1 dell-per740-32.rhts.eng.pek2.redhat.com Ready master 3h32m v1.21.11+31d53a1 dell-per740-35.rhts.eng.pek2.redhat.com Ready worker 157m v1.21.11+31d53a1
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.8.49 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:6308