mirror of https://github.com/k3s-io/k3s
ac17b239b6
Automatic merge from submit-queue rkt: Don't return if the service file doesn't exist when killing the pod Remove an unused logic. Also this prevents the KillPod() from failing when the service file doesn't exist. E.g., it can be removed by garbage collection in a rare case: 1, There are already more than `gcPolicy.MaxContainers` containers running on the host. 2, The new pod(A) starts to run but doesn't enter 'RUNNING' state yet. 3, GC is triggered, and it sees the pod(A) is in an inactive state (not running), and the it needs to remove the pod to force the `gcPolicy.MaxContainers`. 4, GC fails to remove the pod because `rkt rm` fails when the pod is running, but it removes the service file anyway. 5, Follow up KillPod() call will fail because it cannot find the service file on disk. Also this is possible only when the pod has been in prepared state for longer than 1 min, which sounds like another issue. cc @kubernetes/sig-rktnetes |
||
|---|---|---|
| .. | ||
| mock_os | ||
| cap.go | ||
| config.go | ||
| container_id.go | ||
| doc.go | ||
| fake_rkt_interface_test.go | ||
| image.go | ||
| log.go | ||
| rkt.go | ||
| rkt_test.go | ||
| systemd.go | ||
| version.go | ||