*** Bug 2015835 has been marked as a duplicate of this bug. ***
Hello, I was able to verify it and also created a dedicated dut pod with attached SR-IOV VF's: (shiftstack) [cloud-user@installer-host ~]$ oc get clusterversions.config.openshift.io NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.8.0-0.nightly-2022-01-24-131630 True False 23h Cluster version is 4.8.0-0.nightly-2022-01-24-131630 (shiftstack) [cloud-user@installer-host ~]$ (shiftstack) [cloud-user@installer-host ~]$ (shiftstack) [cloud-user@installer-host ~]$ (shiftstack) [cloud-user@installer-host ~]$ oc get csv -n openshift-sriov-network-operator NAME DISPLAY VERSION REPLACES PHASE performance-addon-operator.v4.8.5 Performance Addon Operator 4.8.5 Succeeded sriov-network-operator.4.8.0-202201210925 SR-IOV Network Operator 4.8.0-202201210925 Succeeded (shiftstack) [cloud-user@installer-host ~]$ (shiftstack) [cloud-user@installer-host ~]$ (shiftstack) [cloud-user@installer-host ~]$ (shiftstack) [cloud-user@installer-host ~]$ oc get all -n openshift-sriov-network-operator NAME READY STATUS RESTARTS AGE pod/network-resources-injector-77phk 1/1 Running 0 53m pod/network-resources-injector-fv2xs 1/1 Running 0 53m pod/network-resources-injector-wbhns 1/1 Running 0 53m pod/sriov-cni-pjfmn 2/2 Running 0 5m9s pod/sriov-device-plugin-kv8hr 1/1 Running 0 3m49s pod/sriov-network-config-daemon-bxltv 1/1 Running 0 53m pod/sriov-network-config-daemon-dv8q7 1/1 Running 0 53m pod/sriov-network-operator-7c98c6cb4-z9cgt 1/1 Running 0 54m NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/network-resources-injector-service ClusterIP 172.30.60.136 <none> 443/TCP 53m NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE daemonset.apps/network-resources-injector 3 3 3 3 3 beta.kubernetes.io/os=linux,node-role.kubernetes.io/master= 53m daemonset.apps/sriov-cni 1 1 1 1 1 beta.kubernetes.io/os=linux,node-role.kubernetes.io/worker= 7m2s daemonset.apps/sriov-device-plugin 1 1 1 1 1 beta.kubernetes.io/os=linux,node-role.kubernetes.io/worker= 7m2s daemonset.apps/sriov-network-config-daemon 2 2 2 2 2 beta.kubernetes.io/os=linux,node-role.kubernetes.io/worker= 53m NAME READY UP-TO-DATE AVAILABLE AGE deployment.apps/sriov-network-operator 1/1 1 1 54m NAME DESIRED CURRENT READY AGE replicaset.apps/sriov-network-operator-7c98c6cb4 1 1 1 54m (shiftstack) [cloud-user@installer-host ~]$ (shiftstack) [cloud-user@installer-host ~]$ (shiftstack) [cloud-user@installer-host ~]$ (shiftstack) [cloud-user@installer-host ~]$ oc get pods NAME READY STATUS RESTARTS AGE dpdk-testpmd 1/1 Running 0 3m57s (shiftstack) [cloud-user@installer-host ~]$ oc logs dpdk-testpmd | grep 'Virtual Function' 0000:00:05.0 'Ethernet Virtual Function 700 Series 154c' drv=vfio-pci unused= 0000:00:06.0 'Ethernet Virtual Function 700 Series 154c' drv=vfio-pci unused= 0000:00:05.0 'Ethernet Virtual Function 700 Series 154c' drv=vfio-pci unused= 0000:00:06.0 'Ethernet Virtual Function 700 Series 154c' drv=vfio-pci unused= (shiftstack) [cloud-user@installer-host ~]$
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.8.29 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:0278