-
Notifications
You must be signed in to change notification settings - Fork 2.7k
[v5.4-rhel] Fix: Ensure HealthCheck exec session terminates on timeout #26456
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
[v5.4-rhel] Fix: Ensure HealthCheck exec session terminates on timeout #26456
Conversation
…sion in the database Fixes: https://issues.redhat.com/browse/RHEL-69970 Fixes: https://issues.redhat.com/browse/RHEL-96916 Fixes: https://issues.redhat.com/browse/RHEL-96917 Signed-off-by: Jan Rodák <[email protected]> (cherry picked from commit ad9839a) Signed-off-by: Jan Rodák <[email protected]>
Previously, the HealthCheck exec session would not terminate on timeout, allowing the healthcheck to run indefinitely. Fixes: https://issues.redhat.com/browse/RHEL-86096 Fixes: https://issues.redhat.com/browse/RHEL-96916 Fixes: https://issues.redhat.com/browse/RHEL-96917 Signed-off-by: Jan Rodák <[email protected]> (cherry picked from commit 499ea11) Signed-off-by: Jan Rodák <[email protected]>
…r timeout is 0 Aligns behavior with documentation stating SIGKILL should be sent immediately if the timeout is zero. Fixes: https://issues.redhat.com/browse/RHEL-96916 Fixes: https://issues.redhat.com/browse/RHEL-96917 Signed-off-by: Jan Rodák <[email protected]> (cherry picked from commit 077649f)
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: Honny1, lsm5 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
if err != nil { | ||
return -1, err | ||
} | ||
session.PID = pid |
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.
In 499ea11#diff-bf52e0a2dfcea051750fa86d05c8a2ce247c66a92a8562570f4d3555d76664a6R872
I'm seeing this line after this one:
session.PIDData = getPidData(pid)
Is that not needed?
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.
This is not needed because we would have to backport this PR #25906.
One Question, otherwise LGTM |
/lgtm |
f944b21
into
containers:v5.4-rhel
Previously, the HealthCheck exec session would not terminate on timeout, allowing the healthcheck to run indefinitely.
Because Docker does that, Podman should kill the HealthCheck when it reaches the timeout.
In order to backport this patch, you need to backport this patch as well (It is included in this PR):
ExecSession
to the database #25003This Backport contains:
ExecSession
to the database #25003Fixes: https://issues.redhat.com/browse/RHEL-96916
Fixes: https://issues.redhat.com/browse/RHEL-96917
Does this PR introduce a user-facing change?