feat: add OCP 5.0 to the version catalogue - #31
Draft
jasonmadigan wants to merge 1 commit into
Draft
Conversation
Pins the 2 Sep nightly carrying the 5.0.0-okd-scos.ec.8 payload. The COPR project runs in devel mode, so recent builds are only indexed in devel/ repodata; both repos are now enabled during the build. Upstream main has moved to 5.1.0, so its RPMs require cri-o >= 5.1.0 while the 5.0 deps mirror ships cri-o 5.0.0. The last 5.0.0-versioned builds are unusable too: they bound cri-o < 1.37.0, and no mirror directory ships cri-o 1.36. Adds DEPS_VERSION to point the deps mirror at 5.1 for this version only, defaulting to OCP_VERSION elsewhere. Closes #30 Signed-off-by: Jason Madigan <jason@jasonmadigan.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adds OCP 5.0 to the catalogue, as the new default.
5.0.0-okd-scos.ec.85.1.0_202609020534_gb19f04dec_5.0.0_okd_scos.ec.8-1.el95.0release-5.0Why the pin needed work
Three combinations were tried before one built:
cri-o >= 5.1.0, but5.0-el9-betaships cri-o 5.0.0.cri-o >= 1.36.0, < 1.37.0, and no deps mirror directory ships cri-o 1.36. ec.6 has the same bound, so every 5.0.0-versioned build is stranded.The deps mirror directory tracks the cri-o the RPM was compiled against, not the payload version. Those coincide for 4.20 through 4.22 and diverge at 5.0, so
DEPS_VERSIONnow overrides the mirror directory, defaulting toOCP_VERSIONwhere they still agree.COPR devel mode
The nightly project creates repositories manually, so its main repodata is frozen at 12 August and every build since then is only indexed under
devel/. Both repos are enabled during the build withskip_if_unavailable=1, and either can satisfy the pin. They index the same physical build directories, so nothing downloads twice.Verification
Built locally for arm64 from this branch:
release.basereports5.1.0-0.nightlyrather than a 5.0 tag. The shipped 4.22 image shows the same skew, so that field tracks main's rebase target while the OKD tag in the RPM name is the payload identity.Not booted as a cluster. Images do not exist on GHCR until the build workflow runs.
Follow-up
gh workflow run images.yml -f version=5.0Closes #30