mirror of
https://github.com/kata-containers/kata-containers.git
synced 2026-07-10 15:56:47 +00:00
7053d70acf
TestKilledVmmCleanup SIGKILLs the VMM and then removes the pod. After a hard VMM kill the shim exits promptly (which the test asserts), so the container's TaskExit event may not have reached containerd before the shim was gone, leaving CRI's view of the container as "running" and making a plain `crictl rmp` fail with "container is still running, to stop first". Retry the normal removal a few times to give the event time to arrive, and only fall back to `crictl rmp -f` if it keeps failing -- which is how a crashed sandbox is recovered in practice (kubelet GC / manual force removal). The essential guarantee, that no shim process is leaked after the VMM is killed, is unchanged. Signed-off-by: Fabiano Fidêncio <ffidencio@nvidia.com>