-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
🐛 CAPD: change the haproxy entrypoint to prevent getting stopped immediately after start #8685
🐛 CAPD: change the haproxy entrypoint to prevent getting stopped immediately after start #8685
Conversation
/test ? |
@chrischdi: The following commands are available to trigger required jobs:
The following commands are available to trigger optional jobs:
Use
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. |
/test pull-cluster-api-e2e-full-main |
1fb425b
to
294f89d
Compare
/test pull-cluster-api-e2e-full-main |
0b76bc8
to
ed2c3a7
Compare
/test pull-cluster-api-e2e-informing-main |
3 similar comments
/test pull-cluster-api-e2e-informing-main |
/test pull-cluster-api-e2e-informing-main |
/test pull-cluster-api-e2e-informing-main |
4baad7d
to
053cc07
Compare
/test pull-cluster-api-e2e-full-main |
…ately after start With this PR CAPD uses a customized entrypoint to start the haproxy lb container. Compared to the entrypoint built-in into the image, it drops the arguments `-sf 7`. This argument seems to result in stopping the container immediately on hard to reproduce circumstances.
053cc07
to
a0c371c
Compare
/test pull-cluster-api-e2e-full-main |
/test pull-cluster-api-e2e-full-main Let's give it a full run before merging |
|
/hold For e2e-full |
/retest |
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
LGTM label has been added. Git tree hash: d19b928ef2c5184d0288732a34da46402f6852cf
|
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbueringer 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 |
/cherry-pick release-1.3 |
/cherry-pick release-1.4 |
We should hold the cherry-picks until we have some signal that this works - but I'd prefer to have them in the queue as a reminder. |
@killianmuldoon: new pull request created: #8741 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. |
@killianmuldoon: new pull request created: #8742 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. |
/area provider/infrastructure-docker |
What this PR does / why we need it:
For more context see #8641.
We came to the conclusion that we can drop the
-sf 7
arguments when starting haproxy.This seem to be able to exit the haproxy process immediately after start, resulting in not-running lb container and by that in flaky tests.
Kudos to @killianmuldoon for testing the updated arguments to see if config updating still works.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Tries to fix #8641