-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sriov-device-plugin cannot be created #259
Comments
Hi, |
Martinkennelly, Thanks for help. The full configmap is appended as follows: apiVersion: v1 The log for the daemon set is appended as Name: kube-sriov-device-plugin-amd64-ph6hl Warning BackOff 61s (x25270 over 3d18h) kubelet, hp3 Back-off restarting failed container The k8 on master node is v1.18.1 and the one on the slave node (HP6) is v1.18.6. The lspci on hp6 is 21:00.0 Network controller [0280]: Mellanox Technologies MT27500 Family [ConnectX-3] [15b3:1003] 21:00.1 Network controller [0280]: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] [15b3:1004] 21:00.2 Network controller [0280]: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] [15b3:1004] 21:00.3 Network controller [0280]: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] [15b3:1004] 21:00.4 Network controller [0280]: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] [15b3:1004] |
I finally found out the problem with the configMap: the "kube-sriov-device-plugin" pod can be correctly created when I add " \"IsRdma\": true" to the "mlnx_sriov_networkdevice" resource as follows: { I don't know why, but it allows the device plugin to be created. |
Good to hear. |
Hi There, Also i think we would need the device plugin pod logs for more logging info. ( Also in the devices entry you need to provide the VF's PCI device ID which is |
we did enabled it to one customer so it should work, you need to know how to use it with VF selector |
+1, The log of sriov-device-plugin daemon when |
Also if you merged this #226 we can see the issue with isRdma |
thank @adrianchiris and @zshi-redhat. I finally get it work. I made two errors in my configMap: 1) use PF ID instead of VF ID; and 2) I didn't delete the comma following last item in IB configuration when I deleted the "isRama" item, but there is no error when I create the map. Right now, the device plugin daemonset works with or without the "isRdma" item specified. |
@moshe010 thanks. If possible, could you point me to some examples on VF selector? |
The 2) explains why the device plugin pod crashed. it failed to parse the configMap in the wrong format. |
What issue would you like to bring attention to
I tried to attach a VF of Mellanox IB interface to a pod. However, when I added one item to the ConfigMap.yaml as follows:
I tried to run Daemonset by the command "kubectl apply -f deployments/k8s-v1.16/sriovdp-daemonset.yaml", the kube-sriov-device-plugin pod can not be created. What's wrong with the the configMap.yaml? Any help is appreciated!
What is the impact of this issue?
Do you have a proposed response or remediation for the issue?
The text was updated successfully, but these errors were encountered: