-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
play kube: notifyproxy: listen before starting the pod #16118
Conversation
[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 |
Needs more work. I'll tackle that tomorrow. |
2edb04c
to
4acc736
Compare
Starting listening for the READY messages on the sdnotify proxies before starting the Pod. Otherwise, we may be missing messages. [NO NEW TESTS NEEDED] as it's hard to test this very narrow race. Related to but may not be fixing containers#16076. Signed-off-by: Valentin Rothberg <[email protected]>
4acc736
to
7b84a3a
Compare
@containers/podman-maintainers PTAL |
LGTM |
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
@edsantiago guess this needs to be cherrypicked to v4.3? I can add this as a patch to the rpm |
This is part of v4.3 but apparently not sufficient to fully fix the flake. Can you try restarting the gating tests? |
Starting listening for the READY messages on the sdnotify proxies before starting the Pod. Otherwise, we may be missing messages.
[NO NEW TESTS NEEDED] as it's hard to test this very narrow race.
Related to but may not be fixing #16076.
Signed-off-by: Valentin Rothberg [email protected]
Does this PR introduce a user-facing change?