Victor, for the policy cannot be created issue, could you please provide the log of sriov-operator-webhook and sriovnetworknodestate CRs?
*** Bug 2016333 has been marked as a duplicate of this bug. ***
Hi, Ziv Could you help verify bug on Openshift deployed on openstack cluster ?
Hello, I was able to verify it and also created a dedicated dut pod with attached Intel X710 SR-IOV VF's: (shiftstack) [cloud-user@installer-host ~]$ oc get clusterversions.config.openshift.io NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.10.0-0.nightly-2022-01-31-012936 True False 39h Cluster version is 4.10.0-0.nightly-2022-01-31-012936 (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.9.5 Performance Addon Operator 4.9.5 Succeeded sriov-network-operator.4.10.0-202201310820 SR-IOV Network Operator 4.10.0-202201310820 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-c4w2r 1/1 Running 0 19m pod/network-resources-injector-fqhch 1/1 Running 0 19m pod/network-resources-injector-l9vsl 1/1 Running 0 19m pod/operator-webhook-bvfl6 1/1 Running 0 19m pod/operator-webhook-qr6j9 1/1 Running 0 19m pod/operator-webhook-wm4xx 1/1 Running 0 19m pod/sriov-device-plugin-qc29t 1/1 Running 0 11m pod/sriov-network-config-daemon-cf8gj 3/3 Running 0 19m pod/sriov-network-config-daemon-csdrh 3/3 Running 0 19m pod/sriov-network-operator-6d94cbc597-phvxs 1/1 Running 0 20m NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/network-resources-injector-service ClusterIP 172.30.133.207 <none> 443/TCP 19m service/operator-webhook-service ClusterIP 172.30.181.240 <none> 443/TCP 19m 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 19m daemonset.apps/operator-webhook 3 3 3 3 3 beta.kubernetes.io/os=linux 19m daemonset.apps/sriov-device-plugin 1 1 1 1 1 beta.kubernetes.io/os=linux,node-role.kubernetes.io/worker= 12m daemonset.apps/sriov-network-config-daemon 2 2 2 2 2 beta.kubernetes.io/os=linux,node-role.kubernetes.io/worker= 19m NAME READY UP-TO-DATE AVAILABLE AGE deployment.apps/sriov-network-operator 1/1 1 1 20m NAME DESIRED CURRENT READY AGE replicaset.apps/sriov-network-operator-6d94cbc597 1 1 1 20m (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 11m (shiftstack) [cloud-user@installer-host ~]$ (shiftstack) [cloud-user@installer-host ~]$ (shiftstack) [cloud-user@installer-host ~]$ (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= Thanks, Ziv
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.10.3 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:0056