-
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
🌱 Add retry to clusterctl UpgradeWithBinary
#11478
🌱 Add retry to clusterctl UpgradeWithBinary
#11478
Conversation
Skipping CI for Draft Pull Request. |
/test help |
@chrischdi: The specified target(s) for
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-sigs/prow repository. |
/test pull-cluster-api-e2e-main |
test/framework/clusterctl/client.go
Outdated
var exitErr *exec.ExitError | ||
if errors.As(err, &exitErr) { | ||
stdErr = string(exitErr.Stderr) | ||
Eventually(func() error { |
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.
let's use a for loop and make the number of retries dependent on the clusterctl version used (>= v1.7.0 should not do any retries)
a8bc7ba
to
a9d315e
Compare
/test pull-cluster-api-e2e-main |
a9d315e
to
624e2a5
Compare
/retest |
624e2a5
to
2c9caab
Compare
/lgtm /hold so you can merge once your happy (I'm okay). What are the plans for cherry-picking this? |
LGTM label has been added. Git tree hash: 6b061c28b313be733d72192aea3fee311bc0d5df
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: chrischdi 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 |
i think cherry-pick onto all tested release branches (1.7, 1.8, 1.9) does that make sense to you? |
/unhold |
Sounds good. |
/cherry-pick release-1.9 |
@cahillsf: new pull request created: #11539 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 |
@cahillsf: new pull request created: #11541 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.7 |
@cahillsf: new pull request created: #11542 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:
adds some retry cushion to clusterctl upgrade
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Related to: #11133 (comment)
/area e2e-testing