-
Notifications
You must be signed in to change notification settings - Fork 1.1k
[1.20] Set systemd property KillMode to mixed for containers #4539
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[1.20] Set systemd property KillMode to mixed for containers #4539
Conversation
Codecov Report
@@ Coverage Diff @@
## release-1.20 #4539 +/- ##
================================================
+ Coverage 40.60% 40.62% +0.01%
================================================
Files 117 117
Lines 9446 9450 +4
================================================
+ Hits 3836 3839 +3
- Misses 5177 5178 +1
Partials 433 433 |
|
/test integration_fedora |
We want systemd to only send SIGTERM to the main process on stop and let that process forward the signal. Today, we have seen issues where the main process forwards the signal in addition to systemd sending it directly leading to failures in graceful shutdown. Signed-off-by: Mrunal Patel <[email protected]>
f7f6754 to
8164338
Compare
saschagrunert
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mrunalp, saschagrunert The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/lgtm |
Signed-off-by: Mrunal Patel [email protected]
What type of PR is this?
/kind bug
What this PR does / why we need it:
This PR sets the systemd KillMode for container scopes to mixed
so on stop, only the main process gets the SIGTERM and is
responsible for forwarding it if needed to child processes.
Without this, we end up with double SIGTERMS leading to unexpected
failures in graceful termination on node shutdown or reboot.
Which issue(s) this PR fixes:
https://bugzilla.redhat.com/show_bug.cgi?id=1882750
Special notes for your reviewer:
Does this PR introduce a user-facing change?