chore: update main to ubi10/nodejs-24-minimal:10.2-1789045317 from ubi10/nodejs-24-minimal:10.2-1788245909 [skip-build] [skip-e2e] - #5384
Merged
openshift-ci[bot] merged 1 commit intoSep 11, 2026
Conversation
…i10/nodejs-24-minimal:10.2-1788245909 [skip-build] [skip-e2e] Signed-off-by: rhdh-bot service account <rhdh-bot@redhat.com>
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
@github-actions[bot]: github-actions[bot] unauthorized: /override is restricted to Repo administrators, approvers in top level OWNERS file, and the following github teams:. DetailsIn 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. |
Contributor
|
openshift-ci
Bot
deleted the
chore/automated-update-base-images-1789154241
branch
September 11, 2026 19:29
openshift-ci Bot
pushed a commit
that referenced
this pull request
Sep 14, 2026
…5390) main has been red since fbd9a52. The hermetic build fails on both arches at the skeleton stage: Problem: conflicting requests - nothing provides xz-libs(x86-64) = 1:5.6.2-4.el10_2.1 needed by xz-1:5.6.2-4.el10_2.1.x86_64 #5384 bumped only the runner image, nodejs-24-minimal, from 10.2-1788245909 to 10.2-1789045317. The skeleton stays on nodejs-24:10.2-1788939823, and that is not an oversight: nodejs-24 has no newer tag, so the two images cannot be aligned right now. rpm-lockfile-prototype resolves against the Containerfile and drops whatever the base images already ship. Regenerated against the newer minimal image (#5389) it dropped xz-libs entirely — 4 occurrences before, 0 after — while keeping xz. The failing dnf install runs in the skeleton stage, on the older image, where that xz-libs is not present. Reverting both files together restores d1dbd50's combination, which built green at 17:55. Bumping the minimal image again should wait until nodejs-24 gets a matching build, so the lockfile can be resolved against a consistent pair. Neither PR built this combination before it landed: #5384 carried [skip-build], and #5389's own "Build Image (Hermetic)" step reports skipped, so its green check never compiled anything. Co-authored-by: Claude Opus 5 <noreply@anthropic.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.
Signed-off-by: rhdh-bot service account rhdh-bot@redhat.com