-
Notifications
You must be signed in to change notification settings - Fork 4.8k
OCPBUGS-86922: Retry transient API errors in pod-network-avalibility preparation #31253
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
Closed
mkowalski
wants to merge
1
commit into
openshift:main
from
mkowalski:fix/pod-network-avalibility-retry-transient-errors
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
@copilot, is this even relevant given this is running only on temporary clusters created for CI purposes?
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.
@copilot you there?
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.
The
context.Background()usage isn't a regression — the original code already usedcontext.Background()for all theseCreate()calls before this PR. This change only wraps them in retry logic without altering the context behavior.That said, the broader point about context propagation: this code runs exclusively in CI on ephemeral clusters. If a job is aborted, the entire cluster gets destroyed — there's nothing to "gracefully cancel" into. The worst case is ~60s of retries against an API server that's about to be torn down anyway.
I could thread
ctxthroughcreateWithRetryand switch toExponentialBackoffWithContext, but it adds signature complexity for zero practical benefit in this context. Happy to do it if reviewers feel strongly, but I'd rather keep the helper simple.🤖 This comment was posted by OpenClaw on behalf of @mkowalski.