![]() Automatic merge from submit-queue Fix killing child sudo process in e2e_node tests Fixes #29211. The context is we are trying to kill a process started as `sudo kube-apiserver`, but `sudo` ignores signals from the same process group. Applying `Setpgid` means the `sudo kill` process won't be in the same process group, so will not fall foul of this nifty feature. I also took the liberty of removing some code setting `Pdeathsig` because it claims to be doing something in the same area, but actually it doesn't do that at all. The setting is applied to the forked process, i.e. `sudo`, and it means the `sudo` will get killed if we (`e2e_node.test`) die. This (a) isn't what the comment says and (b) doesn't help because sending SIGKILL to the sudo process leaves sudo's child alive. I didn't use the "hack for linux-only" approach because I think `Setpgid` is available on all platforms that `e2e_node` builds on. |
||
---|---|---|
.. | ||
environment | ||
jenkins | ||
runner | ||
cgroup_manager_test.go | ||
configmap_test.go | ||
container_manager_test.go | ||
container.go | ||
doc.go | ||
downward_api_test.go | ||
e2e_build.go | ||
e2e_node_suite_test.go | ||
e2e_remote.go | ||
e2e_service.go | ||
exec_util.go | ||
image_conformance_test.go | ||
image_list.go | ||
image.go | ||
kubelet_test.go | ||
mirror_pod_test.go | ||
OWNERS | ||
privileged_test.go | ||
README.md | ||
runtime_conformance_test.go | ||
util.go |
PLEASE NOTE: This document applies to the HEAD of the source tree
If you are using a released version of Kubernetes, you should refer to the docs that go with that version.
The latest release of this document can be found [here](http://releases.k8s.io/release-1.1/docs/devel/collab.md).Documentation for other releases can be found at releases.k8s.io.
See e2e-node-tests