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
Step 3: Delete the sriov-device-plugin-7wkm8 pod of node on which step 2 payload is running on.
kubectl delete po sriov-device-plugin-7wkm8 -n sriov-network-operator
Then, the sriov-device-plugin daemonset will auto launch a new pod you just deleted.
Step 4: Now the node Capacity/Allocatable of VF num NOT correct, show me 7, NOT 8. Why?
Anything else we need to know?
Yeah!
I add some debug code to sriov-network-device-plugin,
It's filterd by linkTypes list, code location: pkg/netdevice/netDeviceProvider.go#GetFilteredDevices()
and, pkg/resources/deviceSelectors.go#func (s *linkTypeSelector) Filter, linkType := dev.(types.PciNetDevice).GetLinkType(), linkType is empty.
And, the final root cause is pkg/netdevice/pciNetDevice.go#func NewPciNetDevice(...)
And repeat the step 1,2,3,4..., Everything is OK, the vf number is 8, NOT 7.
So, My Question is, what's the difference between add k8s.v1.cni.cncf.io/networks to annotations and NOT.
So, My Question is, what's the difference between add k8s.v1.cni.cncf.io/networks to annotations and NOT.
So, My Question is, what's the difference between add k8s.v1.cni.cncf.io/networks to annotations and NOT.
Component Versions
Please fill in the below table with the version numbers of components used.
Component
Version
SR-IOV Network Device Plugin
3.5.1
SR-IOV CNI Plugin
sriovCni:v2.6.3; ibSriovCni: v1.0.2
Multus
Not sure
Kubernetes
v1.23.10
OS
Ubuntu 20.04 Kernel 5.4.0-42-generic
sriov-operator
v1.2.0
Config Files
Config file locations may be config dependent.
Device pool config file location (Try '/etc/pcidp/config.json')
What happened?
Node Capacity/Allocatable of VF num NOT correct
What did you expect to happen?
Expected numVfs is : 8
What are the minimal steps needed to reproduce the bug?
Step 1: Deploy sriov-network-operator 1.2.1
Step 2: Deploy a payload:
Step 3: Delete the
sriov-device-plugin-7wkm8
pod of node on which step 2 payload is running on.Then, the
sriov-device-plugin
daemonset will auto launch a new pod you just deleted.Step 4: Now the node Capacity/Allocatable of VF num NOT correct, show me 7, NOT 8. Why?
Anything else we need to know?
Yeah!
I add some debug code to sriov-network-device-plugin,
It's filterd by linkTypes list, code location:
pkg/netdevice/netDeviceProvider.go#GetFilteredDevices()
and,
pkg/resources/deviceSelectors.go#func (s *linkTypeSelector) Filter
,linkType := dev.(types.PciNetDevice).GetLinkType()
, linkType is empty.And, the final root cause is
pkg/netdevice/pciNetDevice.go#func NewPciNetDevice(...)
The
len(netDevs) == 0
, because the/sys/bus/pci/devices/0000:12:00.5/net
directory is empty.and other vf director is seems OK, like below:
And if I removed the
spec.template.metadata.annotations
And repeat the step 1,2,3,4..., Everything is OK, the vf number is 8, NOT 7.
So, My Question is, what's the difference between add
k8s.v1.cni.cncf.io/networks
to annotations and NOT.So, My Question is, what's the difference between add
k8s.v1.cni.cncf.io/networks
to annotations and NOT.So, My Question is, what's the difference between add
k8s.v1.cni.cncf.io/networks
to annotations and NOT.Component Versions
Please fill in the below table with the version numbers of components used.
Config Files
Config file locations may be config dependent.
Device pool config file location (Try '/etc/pcidp/config.json')
Multus config (Try '/etc/cni/multus/net.d')
CNI config (Try '/etc/cni/net.d/')
Kubernetes deployment type ( Bare Metal, Kubeadm etc.)
Kubeconfig file
SR-IOV Network Custom Resource Definition
Logs
SR-IOV Network Device Plugin Logs (use
kubectl logs $PODNAME
)Multus logs (If enabled. Try '/var/log/multus.log' )
Kubelet logs (journalctl -u kubelet)
The text was updated successfully, but these errors were encountered: