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
Bug 1914402: ipsec: Add liveness probe #952
Bug 1914402: ipsec: Add liveness probe #952
Conversation
/bugzilla refresh |
@markdgray: This pull request references Bugzilla bug 1914402, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@markdgray: This pull request references Bugzilla bug 1914402, which is valid. 3 validation(s) were run on this bug
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
0fd4078
to
b0bded8
Compare
ipsec is failing with some kind of aws quota /retest |
unrelated panic in ipsec case /retest |
In the case of failure of ipsec daemons, add liveness probe to detect so that the kubelet can restart the container. Signed-off-by: Mark Gray <mark.d.gray@redhat.com>
Currently, the readiness probe only checks for failures of the 'ovs-monitor-ipsec' daemon. Signed-off-by: Mark Gray <mark.d.gray@redhat.com>
6537df1
to
353a902
Compare
/lgtm |
unrelated panic in pods/openshift-operator-lifecycle-manager_packageserver for ipsec job /retest |
ipsec: looks unrelated. machine config operator and one worker node was not ready. /test e2e-ovn-ipsec-step-registry |
ipsec has passed. As this PR is only for the case when IPsec is enabled. Any other failures are unrelated. /retest |
1 similar comment
ipsec has passed. As this PR is only for the case when IPsec is enabled. Any other failures are unrelated. /retest |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: astoycos, dcbw, markdgray 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 |
@markdgray: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
/retest Please review the full test history for this PR and help us cut down flakes. |
@markdgray: All pull requests linked via external trackers have merged: Bugzilla bug 1914402 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
In the case of failure of ipsec daemons, add liveness
probe to detect so that the kubelet can restart the
container.
Signed-off-by: Mark Gray mark.d.gray@redhat.com