Skip to content
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

health checks: make on-failure action retry aware #16084

Merged
merged 1 commit into from
Oct 7, 2022

Conversation

vrothberg
Copy link
Member

Make sure that the on-failure actions only kick in once the health check has passed its retries.

Signed-off-by: Valentin Rothberg [email protected]

Does this PR introduce a user-facing change?

Make sure that the on-failure actions only kick in once the health check has passed its retries.

@mheon PTAL

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 7, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vrothberg

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 7, 2022
@rhatdan
Copy link
Member

rhatdan commented Oct 7, 2022

LGTM

libpod/healthcheck.go Outdated Show resolved Hide resolved
libpod/healthcheck.go Outdated Show resolved Hide resolved
Make sure that the on-failure actions only kick in once the health check
has passed its retries.  Also fix race conditions on reading/writing the
log.

Signed-off-by: Valentin Rothberg <[email protected]>
Copy link
Member

@Luap99 Luap99 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mheon
Copy link
Member

mheon commented Oct 7, 2022

LGTM

@mheon
Copy link
Member

mheon commented Oct 7, 2022

/lgtm
/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 7, 2022
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 7, 2022
@mheon
Copy link
Member

mheon commented Oct 7, 2022

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 7, 2022
@openshift-merge-robot openshift-merge-robot merged commit 5908996 into containers:main Oct 7, 2022
openshift-merge-robot added a commit that referenced this pull request Oct 9, 2022
openshift-merge-robot added a commit that referenced this pull request Oct 10, 2022
[v4.1.1-rhel] Backported #16084 to v4.1.1-rhel
@TomSweeneyRedHat
Copy link
Member

Follow up fix for https://bugzilla.redhat.com/show_bug.cgi?id=2097708

@vrothberg vrothberg deleted the health-check-fix branch October 11, 2022 06:45
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 20, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 20, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. release-note
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants