VFs may get reseted after being allocated by other pod about sriov-cni HOT 6 CLOSED

Script and manifests I used in order to reproduce this https://gist.github.com/ormergi/3ddbf901ddc95baf316b604994285a69.
Journal log from one of the iterations when the issue occurred https://pastebin.com/eGhyrevk.

from sriov-cni.

Hi @ormergi can this be related to #126 ?

from sriov-cni.

@SchSeba thanks for looking at this.
It seems that #126 is about kubelet won't keep the pod alive so that the plugin will manage to reach its netns and do its thing.
In our case, the plugin executes as we can see the VFs get reset after the pod is allegedly disposed though.

from sriov-cni.

@ormergi will you be able to provide the logs from multus? that is the only way we will be able to try and trace the issue I think

from sriov-cni.

Script and manifests I used in order to reproduce this https://gist.github.com/ormergi/3ddbf901ddc95baf316b604994285a69. Journal log from one of the iterations when the issue occurred https://pastebin.com/eGhyrevk.

@SchSeba are these logs good enough https://pastebin.com/eGhyrevk?
This is a journal log of the node since the pod was created + 1 minute before, it also includes Multus logs.

EDIT: FWIW its much easier to review these logs in vscode.

from sriov-cni.

@adrianchiris is there a planned release so we could consume the fixed version? 🙂

from sriov-cni.