Bug 2012836

Summary: SRIOV-CNI failed to load netconf: LoadConf(): the VF 0000:1a:09.6 does not have a interface name or a dpdk driver
Product: OpenShift Container Platform Reporter: Christoffer Back <cback>
Component: NetworkingAssignee: zenghui.shi <zshi>
Networking sub component: SR-IOV QA Contact: zhaozhanqi <zzhao>
Status: CLOSED DUPLICATE Docs Contact:
Severity: medium    
Priority: medium CC: bradnichols, cgoncalves, dosmith, fromani, igreen, keyoung, mschmidt, sscheink
Version: 4.8   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-01-20 09:51:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2003193, 2025329, 2026386, 2026388, 2028126, 2028127, 2078400    
Bug Blocks:    

Comment 1 zenghui.shi 2021-10-15 07:34:09 UTC 
Christoffer, which deviceType is used in the sriov policy? Is it netdevice?

SR-IOV CNI tries to find a kernel interface name (/sys/bus/pci/devices/<vf-pci-addr>/net) or the dpdk driver (/sys/bus/pci/devices/<vf-pci-addr>/driver) given a VF PCI address (0000:1a:09.6), the below error indicates that neither of them is found. Could you check these two paths while the issue happens? I suspect it is also a driver related issue which take a relatively long time for the VF device to become ready.

"SRIOV-CNI failed to load netconf: LoadConf(): the VF 0000:1a:09.6 does not have a interface name or a dpdk driver"
Comment 22 Sebastian Scheinkman 2022-01-20 09:51:58 UTC 

*** This bug has been marked as a duplicate of bug 2026388 ***