-
Notifications
You must be signed in to change notification settings - Fork 1.4k
🌱 Attempt older version upgrades twice to work around flake with the docker controller #11759
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
🌱 Attempt older version upgrades twice to work around flake with the docker controller #11759
Conversation
…e docker controller Signed-off-by: cprivitere <[email protected]>
c3585e6
to
e6bb305
Compare
Thanks! /lgtm |
LGTM label has been added. Git tree hash: d6a7cb7b308a1d865df535395ec61baa0f1b541d
|
Thank you! /lgtm |
[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.9 |
@cprivitere: new pull request created: #11793 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-sigs/prow repository. |
/cherry-pick release-1.8 |
@cprivitere: #11759 failed to apply on top of branch "release-1.8":
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-sigs/prow repository. |
What this PR does / why we need it: This is a recommendation from this comment #11610 (comment) in #11610 to work around flaky upgrade tests and improve our CI signal. The root cause seems to be related to the docker controller but only affects older versions. So the goal is to just reduce the flakey signal by retrying the tests on those older versions (which just show up in our upgrade tests).
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #11209
Fixes #11610
/area e2e-testing