-
Notifications
You must be signed in to change notification settings - Fork 3
Use oc adm release extract --tools to download OCP binaries instead of release-controller file-cache #15
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
Open
tusharjadhav3302
wants to merge
3
commits into
main
Choose a base branch
from
use-oc-adm-release-extract-for-binaries
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+149
−30
Open
Use oc adm release extract --tools to download OCP binaries instead of release-controller file-cache #15
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
bda356e
Use oc adm release extract --tools instead of unreliable file-cache f…
tusharjadhav3302 7756aed
Add pull secret extraction fallback and diagnostics for CI debugging
tusharjadhav3302 35985b8
Use curl + kubeconfig certs for pull secret and bootstrap oc from mir…
tusharjadhav3302 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
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
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.
This
set_factis inside thewhen: build_name == ''block, so it only fires for nightly and 4-stable. The channel path (candidate/fast/stable/eus, lines 55-74) and the specific-build path (lines 46-51) don't setopenshift_release_pull_spec, which meansget_openshift_release_binaries.ymlwould fail for every job usingopenshift_build_name: "candidate"- that's 6 of 13 job definitions.For channel builds,
release.txtalready has aPull From:field (quay.io/openshift-release-dev/ocp-release@sha256:...) that could be parsed here. For specific builds, a fallback constructing the pull spec fromopenshift_release_build_namewould cover the rest.Uh oh!
There was an error while loading. Please reload this page.
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.
Yes , this was indeed a gap. Fixed in the latest push:
Channel builds (candidate/fast/stable/eus): The release.txt file already has a
Pull From:field with a digest-pinned pull spec (e.g. quay.io/openshift-release-dev/ocp-release@sha256:...). Added a task to parse it withgrep '^Pull From:' | awk '{print $3}'and setopenshift_release_pull_specfrom it.Specific builds: Wrapped the existing
set_factin a block and added pull spec construction — nightly builds useregistry.ci.openshift.org/ocp/release:<build_name>, GA builds usequay.io/openshift-release-dev/ocp-release:<build_name>-x86_64.All three code paths now set
openshift_release_pull_specbeforeget_openshift_release_binaries.ymlruns.