I'm facing a similar issue to #14. The device plugin worked once, but the device plugin has not allocated a VF to a pod due to insufficient rdma/vhca after recreating the pod. Then, I tried to disable and enable SR-IOV and to reload the driver, but it doesn't work.
Here is the log on the device plugin.
$ kubectl logs --namespace=kube-system rdma-sriov-dp-ds-9t5gs
2020/03/05 08:07:13 Starting K8s RDMA SRIOV Device Plugin version= 0.2
2020/03/05 08:07:13 Starting FS watcher.
2020/03/05 08:07:13 Starting OS watcher.
2020/03/05 08:07:13 Reading /k8s-rdma-sriov-dev-plugin/config.json
2020/03/05 08:07:13 loaded config: {"mode":"sriov","pfNetdevices":["enp96s0f0"]}
2020/03/05 08:07:13 sriov device mode
Configuring SRIOV on ndev= enp96s0f0 9
max_vfs = 4
cur_vfs = 4
vf = &{2 virtfn2 true false}
vf = &{0 virtfn0 false false}
Fail to config vfs for ndev = enp96s0f0
Fail to configure sriov; error = Link not found
2020/03/05 08:07:13 Starting to serve on /var/lib/kubelet/device-plugins/rdma-sriov-dp.sock
2020/03/05 08:07:13 Registered device plugin with Kubelet
exposing devices: []
The device plugin would be the latest version. But I don't know why the digest ID is not different from one on Dockerhub and it doesn't start when indicating the same digest ID on Dockerhub in the manifest.
I'm facing a similar issue to #14. The device plugin worked once, but the device plugin has not allocated a VF to a pod due to
insufficient rdma/vhca
after recreating the pod. Then, I tried to disable and enable SR-IOV and to reload the driver, but it doesn't work.Here is the log on the device plugin.
Kubernetes version is
The device plugin would be the latest version. But I don't know why the digest ID is not different from one on Dockerhub and it doesn't start when indicating the same digest ID on Dockerhub in the manifest.