You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OpenShift cluster, Mellanox ConnectX-5 configured in switchdev mode using sriov-network-operator, VFs can be observed on the target worker node, but device plugin fail to detect VFs with pfName nicSelector, which results in zero resource reported in node status.
It is noticed that when VF is released from sriov pod, its representor name appears as the first element in the host directory as below (because of the naming convention):
# ls /sys/bus/pci/devices/0000\:d8\:01.5/physfn/net/
58609951635cbfa ens8f1 ens8f1_0 ens8f1_1 ens8f1_3 ens8f1_4 ens8f1_5
0000:d8:01.5: the VF PCI address
58609951635cbfa: the VF representor name after its VF released from sriov pod
ens8f1: PF name of the VF.
This 58609951635cbfa name is considered as the PF name when utils.GetPfName is called, which of course doesn't match with the pfName specified in the device plugin config, this in turn results in VFs be filtered out from the resource pool.
What did you expect to happen?
VFs in switchdev mode be detected successfully using pfNames selector.
What are the minimal steps needed to reproduce the bug?
Deploy a baremetal kubernetes cluster with one of the workers containing Mellanox CX-5 card
Deploy sriov-network-operator and apply sriov network node policy (use pfName in the nicSelector field) to configure VFs in switchdev mode on CX-5 interface
Observe that VFs resource been reported to node status
Create sriov pod requesting VF resource, delete the pod once it is successfully created
Restart sriov network device plugin manually (delete the device plugin pod on target node)
Observe that zero number of resource be reported by sriov device plugin
Component Versions
Component
Version
SR-IOV Network Device Plugin
master
SR-IOV CNI Plugin
master
OS
4.18.0-341.el8.x86_64
Config Files
Config file locations may be config dependent.
Device pool config file location (Try '/etc/pcidp/config.json')
What happened?
OpenShift cluster, Mellanox ConnectX-5 configured in switchdev mode using sriov-network-operator, VFs can be observed on the target worker node, but device plugin fail to detect VFs with pfName nicSelector, which results in zero resource reported in node status.
It is noticed that when VF is released from sriov pod, its representor name appears as the first element in the host directory as below (because of the naming convention):
0000:d8:01.5: the VF PCI address
58609951635cbfa: the VF representor name after its VF released from sriov pod
ens8f1: PF name of the VF.
This 58609951635cbfa name is considered as the PF name when utils.GetPfName is called, which of course doesn't match with the pfName specified in the device plugin config, this in turn results in VFs be filtered out from the resource pool.
What did you expect to happen?
VFs in switchdev mode be detected successfully using pfNames selector.
What are the minimal steps needed to reproduce the bug?
Component Versions
Config Files
Config file locations may be config dependent.
Device pool config file location (Try '/etc/pcidp/config.json')
The text was updated successfully, but these errors were encountered: