mirror of
https://github.com/k3s-io/kubernetes.git
synced 2025-07-30 06:54:01 +00:00
Kill container runtime with SIGKILL
Make sure to use SIGKILL so that the service is killed in a dirty way. In case container runtime use "Restart=on-abnormal" in systemd, killing with SIGTERM will not restart the service, as the kill looks intentional and clean. This is used by cri-o by default.
This commit is contained in:
parent
c5bd36ef90
commit
2787e8c18c
@ -112,7 +112,7 @@ var _ = SIGDescribe("Restart [Serial] [Slow] [Disruptive] [NodeFeature:Container
|
||||
}
|
||||
return nil
|
||||
}, 1*time.Minute, 2*time.Second).Should(gomega.BeNil())
|
||||
if stdout, err := exec.Command("sudo", "kill", fmt.Sprintf("%d", pid)).CombinedOutput(); err != nil {
|
||||
if stdout, err := exec.Command("sudo", "kill", "-SIGKILL", fmt.Sprintf("%d", pid)).CombinedOutput(); err != nil {
|
||||
framework.Failf("Failed to kill container runtime (pid=%d): %v, stdout: %q", pid, err, string(stdout))
|
||||
}
|
||||
// Assume that container runtime will be restarted by systemd/supervisord etc.
|
||||
|
Loading…
Reference in New Issue
Block a user