Description of problem: After worker reboot sriov pod fails to recover, following error is seen in worker journal Feb 22 01:14:34 worker18-ocp1-5gc-n62.sc.sero.gic.ericsson.se hyperkube[6973]: E0222 01:14:34.826247 6973 remote_runtime.go:116] "RunPodSandbox from runtime service failed" err="rpc error: code = Unknown desc = failed to create pod network sandbox k8s_eric-pc-up-data-plane-5d98b75c57-q5nm8_pcg_b77594d3-a310-46e5-914e-0dddfa83da1d_0(873fc4e38b135d8492254ac1859f75b26ee173bd23ddd866b88d21146df1a1cc): error adding pod pcg_eric-pc-up-data-plane-5d98b75c57-q5nm8 to CNI network \"multus-cni-network\": [pcg/eric-pc-up-data-plane-5d98b75c57-q5nm8:eric-pc-up-data-plane-net1]: error adding container to network \"eric-pc-up-data-plane-net1\": SRIOV-CNI failed to load netconf: LoadConf(): failed to get VF information: \"lstat /sys/bus/pci/devices/0000:37:00.0/physfn/net: no such file or directory\"" Version-Release number of selected component (if applicable): OCP 4.8.24 sriov-network-operator.4.8.0-202201261123 How reproducible: Always, after worker reboot Steps to Reproduce: * apply SriovNodePolicy(2vfs on one node) and SriovNetwork * Create Deployment with 2 replicas and created network * reboot the node Actual results: Expected results: Additional info:
- name: SRIOV_DEVICE_PLUGIN_IMAGE value: registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-sriov-network-device-plugin@sha256:4a90d5f188b1c813a09f6273bf2a1ee6779cd386c3ce7fa430fef0a3f579ccf9 4.10.0-rc.5 ======================= Scenario: * apply SriovNodePolicy(2vfs on one node) and SriovNetwork * Create Deployment with 2 replicas and created network * reboot the node * both pods are running after reboot
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.11.0 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:5069