-
Notifications
You must be signed in to change notification settings - Fork 1.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
[release tool] fix hashrelease hanging on image checks #9681
Merged
Conversation
This file contains 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
marvin-tigera
added
release-note-required
Change has user-facing impact (no matter how small)
docs-pr-required
Change is not yet documented
labels
Jan 7, 2025
radTuti
added
docs-not-required
Docs not required for this change
release-note-not-required
Change has no user-facing impact
labels
Jan 7, 2025
marvin-tigera
removed
release-note-required
Change has user-facing impact (no matter how small)
docs-pr-required
Change is not yet documented
labels
Jan 7, 2025
radTuti
commented
Jan 7, 2025
for name, component := range r.imageComponents { | ||
go imgExists(name, component, ch) | ||
} | ||
for range images { |
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.
I think this should be for range r.imageComponents
- the thing is that we're waiting for each started goroutine to finish, and we know we launched r.imageComponents
goroutines. That would probably fix the original deadlock IIUC
coutinhop
reviewed
Jan 8, 2025
coutinhop
approved these changes
Jan 8, 2025
caseydavenport
requested changes
Jan 8, 2025
radTuti
force-pushed
the
hashrelease-fix
branch
from
January 8, 2025 22:04
efeeab9
to
966f7a7
Compare
caseydavenport
approved these changes
Jan 8, 2025
radTuti
added a commit
to radTuti/calico
that referenced
this pull request
Jan 9, 2025
…#9681) * rewrite image check with timeout * pass components list to manager * cleanup * address review feedback
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
docs-not-required
Docs not required for this change
release-note-not-required
Change has no user-facing impact
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.
Description
The components were not being pased on for hashrelease publish leading to the goroutine getting stuck waiting for results.
This adds timeout to each image check, includes more logs and validation checks during that process.
Related issues/PRs
Todos
Release Note
Reminder for the reviewer
Make sure that this PR has the correct labels and milestone set.
Every PR needs one
docs-*
label.docs-pr-required
: This change requires a change to the documentation that has not been completed yet.docs-completed
: This change has all necessary documentation completed.docs-not-required
: This change has no user-facing impact and requires no docs.Every PR needs one
release-note-*
label.release-note-required
: This PR has user-facing changes. Most PRs should have this label.release-note-not-required
: This PR has no user-facing changes.Other optional labels:
cherry-pick-candidate
: This PR should be cherry-picked to an earlier release. For bug fixes only.needs-operator-pr
: This PR is related to install and requires a corresponding change to the operator.