*** Bug 2068183 has been marked as a duplicate of this bug. ***
Verified [kni@provisionhost-0-0 ~]$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.10.0-0.nightly-2022-04-28-030337 True False 2d20h Cluster version is 4.10.0-0.nightly-2022-04-28-030337 [kni@provisionhost-0-0 ~]$ oc get csv -A NAMESPACE NAME DISPLAY VERSION REPLACES PHASE openshift-nmstate kubernetes-nmstate-operator.4.10.0-202204211158 Kubernetes NMState Operator 4.10.0-202204211158 Succeeded # Collect must-gather oc adm must-gather # Install omg pip3 install o-must-gather --user # Check the nmstate data [kni@provisionhost-0-0 ~]$omg use must-gather.local.5448190498349624412 [kni@provisionhost-0-0 ~]$ omg get all -n openshift-nmstate NAME READY STATUS RESTARTS AGE pod/nmstate-cert-manager-7f6f95fb49-45rrk 1/1 Running 0 2d pod/nmstate-handler-6cnqc 1/1 Running 0 2d pod/nmstate-handler-8g7hm 1/1 Running 0 2d pod/nmstate-handler-9r54k 1/1 Running 0 2d pod/nmstate-handler-9r7vq 1/1 Running 0 2d pod/nmstate-handler-btp4p 1/1 Running 0 2d pod/nmstate-operator-ccfdf56fd-k7q7p 1/1 Running 0 2d pod/nmstate-webhook-7cc4ffc5bc-6wdlw 1/1 Running 0 2d pod/nmstate-webhook-7cc4ffc5bc-l9b6b 1/1 Running 0 2d NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/nmstate-webhook ClusterIP 172.30.79.211 <none> 443/TCP 2d NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE daemonset/nmstate-handler 5 5 5 5 5 beta.kubernetes.io/arch=amd64 kubernetes.io/os=linux 2d NAME READY UP-TO-DATE AVAILABLE AGE deployment/nmstate-cert-manager 1/1 1 1 2d deployment/nmstate-operator 1/1 1 1 2d deployment/nmstate-webhook 2/2 2 2 2d NAME DESIRED CURRENT READY AGE replicaset/nmstate-cert-manager-7f6f95fb49 1 1 1 2d replicaset/nmstate-operator-ccfdf56fd 1 1 1 2d replicaset/nmstate-webhook-7cc4ffc5bc 2 2 2 2d
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 (OpenShift Container Platform 4.10.13 bug fix 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/RHBA-2022:1690