-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
None
-
4.9
-
Important
-
None
-
Rejected
-
False
-
-
Description of problem:
SR-IOV Workload Pod stuck at init status with VF load error Below error can be seen within project event log SRIOV-CNI failed to load netconf: LoadConf(): the VF 0000:1a:01.3 does not have a interface name or a dpdk driver They are using a supported NIC & i see all the VF(s) are up. $ lspci | grep "Eth" 18:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Controller E810-C for SFP [8086:1593] (rev 02) Subsystem: Intel Corporation Ethernet Network Adapter E810-XXV-4 [8086:0007] Physical Slot: 1Also, the virtual functions are up $ ip link -s -d 6: ens2f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000 link/ether b4:96:91:b1:e7:04 brd ff:ff:ff:ff:ff:ff promiscuity 1 minmtu 68 maxmtu 9702 addrgenmode none numtxqueues 64 numrxqueues 64 gso_max_size 65536 gso_max_segs 65535 RX: bytes packets errors dropped overrun mcast 57427281960 453943461 0 441285403 0 134863 TX: bytes packets errors dropped carrier collsns 13224340495 15166893 0 0 0 0 vf 0 link/ether fa:d2:81:db:cd:52 brd ff:ff:ff:ff:ff:ff, vlan 1611, spoof checking on, link-state auto, trust off RX: bytes packets mcast bcast dropped 19322 195 31 0 0 TX: bytes packets dropped 164014014 200163 0 vf 1 link/ether 7e:96:f9:a7:49:6d brd ff:ff:ff:ff:ff:ff, vlan 1611, spoof checking on, link-state auto, trust off RX: bytes packets mcast bcast dropped 282242 1895 31 0 0 TX: bytes packets dropped 244874 1489 0 vf 2 link/ether 22:96:d5:0b:0d:f1 brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off RX: bytes packets mcast bcast dropped 273095 823 0 817 823 TX: bytes packets dropped 0 0 0 vf 3 link/ether de:5e:9a:b6:8c:5e brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off RX: bytes packets mcast bcast dropped 350059 1057 0 1046 1057 TX: bytes packets dropped 0 0 0 vf 4 link/ether f6:79:52:28:d4:ab brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off RX: bytes packets mcast bcast dropped 1932437 5796 0 5791 5796 TX: bytes packets dropped 0 0 0 vf 5 link/ether ba:c2:14:23:80:73 brd ff:ff:ff:ff:ff:ff, vlan 1600, spoof checking on, link-state auto, trust off RX: bytes packets mcast bcast dropped 1227516 5752 35 0 0 TX: bytes packets dropped 9186992 9905 0 vf 6 link/ether 8a:58:43:cc:81:6f brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off RX: bytes packets mcast bcast dropped 274563 833 0 818 833 TX: bytes packets dropped 0 0 0 vf 7 link/ether e6:cd:a1:27:9a:22 brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off RX: bytes packets mcast bcast dropped 2050306 6155 0 6131 6155 TX: bytes packets dropped 0 0 0
Version-Release number of selected component (if applicable):
OCP v4.9
How reproducible:
Telco Customer is facing this within their lab environment
Steps to Reproduce:
1. 2. 3.
Actual results:
Pods aren't scheduled with the error Warning FailedCreatePodSandBox 2m21s (x2396 over 11h) kubelet (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_eric-ran-du-baseband-5c48f4b75f-w8q5z_welktxfe-00000001vzwcvdu-y-ec-x-00000000012_fb302b03-9766-4403-a67f-cd0f74668699_0(595bbbbbd4a0ffeafb128a61db6acf7397c30b6338b31ff106fe1b1ecc304558): error adding pod welktxfe-00000001vzwcvdu-y-ec-x-00000000012_eric-ran-du-baseband-5c48f4b75f-w8q5z to CNI network "multus-cni-network": [welktxfe-00000001vzwcvdu-y-ec-x-00000000012/eric-ran-du-baseband-5c48f4b75f-w8q5z/fb302b03-9766-4403-a67f-cd0f74668699:networking-f1u]: error adding container to network "networking-f1u": SRIOV-CNI failed to load netconf: LoadConf(): the VF 0000:1a:01.3 does not have a interface name or a dpdk driver
Expected results:
Pods should be assigned an net1 interface
Additional info: