sriov-network-operator pod not recovered after worker node reboot in RHOCP 4

Solution Verified - Updated -

Issue

  • SR-IOV application Pod in ContainerCreating status after worker node restart
  • SR-IOV operator configured with PF under selector SriovNetworkNodePolicy.spec.nicSelector.pfNames causes application Pod in ContainerCreating status

  • SR-IOV application Pod replica's output log presents the following error:

     Normal AddedInterface 2m18s multus Add eth0 [10.129.10.19/23] from ovn-kubernetes │
│ Warning FailedCreatePodSandBox 2m17s kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox 
  k8s_eric-pc- 
 up-data-plane-5d98b75c57-v9fr2_pcg_9c59cea9-cf72-4ff1-baa9-0870aa63 │
│ f83d_0(b7b5521ce475b672b0b0cbd535f1da787c661a224a6ba09da0ee6fd90d2834ef): error adding pod <pod-name>-5d98b75c57-v9fr2 to CNI network 
  "multus-cni-network": [ns/<podname>-5d98b75c57-v9fr2: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"

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    o 4.11
    o 4.10
    o 4.9
    o 4.8
    o 4.7
  • SR-IOV operator

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content