24c4b351ea
It seems that latest crio versions moved removal of network namespace to later in the container lifecycle. This means that sometimes the network namespace of a container will hang after pod is already gone from the API and Kuryr assigned it's VIF to another pod. This might cause VLAN ID conflicts, but normally that's not an issue as kuryr-daemon is removing interfaces from container namespace on CNI DEL. It may however happen that if kuryr-daemon was down when CNI DEL happened, the info about the VIF saved in KuryrPort will already be gone. In that case we simply returned success to the CNI without doing any unplugging. Now if the netns is not removed immediately after that we might end up with VLAN ID conflicts. This commit makes sure that even if VIF info is gone, kuryr-daemon will at least attempt to remove the container interface from the container netns. This should limit the problem. Change-Id: Ie7d4966473c83554786e79aea0d28a26de902a66 Closes-Bug: 1892388 |
||
---|---|---|
.. | ||
__init__.py | ||
base.py | ||
k8s_cni_registry.py |