Repository navigation
tests: Pin ubi9/podman bound image to 9.8-1793032728 - #2606
Merged
Merged
Conversation
The ubi9/podman 9.8-1793203936 build that now backs :latest on registry.access.redhat.com has no sigstore signature for that registry's :latest (or :9.8) tag; it only carries registry.redhat.io identities plus registry.access.redhat.com :1793203970. CentOS Stream 10's default policy requires sigstoreSigned for registry.access.redhat.com with the default matchRepoDigestOrExact identity, so pulling it by tag on the upgraded guest is rejected and the centos-10 ostree upgrade test fails on every PR. Pin the previous build by digest. The storage check in the logically bound install test looked images up by repository:tag, which a digest reference doesn't have, so look each one up directly. Assisted-by: https://github.com/cgwalters/cgwalters#llms Signed-off-by: Colin Walters <walters@verbum.org>
The digest pinned in the previous commit is the manifest list's, but the install path copies bound images out of host containers-storage with `podman image push`, and the host only holds the per-arch manifest. containers-storage then refuses the copy with "Digest of source image's manifest would not match destination reference". The 9.8-1793032728 tag carries a registry.access.redhat.com signature for that exact identity, so pulling it by tag satisfies the default sigstoreSigned policy and needs no digest. That also lets the logically bound install test go back to matching repository:tag. Assisted-by: https://github.com/cgwalters/cgwalters#llms Signed-off-by: Colin Walters <walters@verbum.org>
cgwalters-bot
force-pushed
the
bot/pin-ubi9-podman
branch
from
October 31, 2026 12:12
ee5ee90 to
03b72b2
Compare
jmarrero
approved these changes
Oct 31, 2026
This was referenced Nov 1, 2026
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
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.
test-upgrade (centos-10, ostree)has failed on every PR since about 2026-10-29 with:The new ubi9/podman build 9.8-1793203936 (
sha256:eabafb0a…) is signed, but its sigstore attachments (sha256-eabafb0a….sig) only carry identities forregistry.redhat.io/ubi9/podman:{latest,9.8,9.8-1793203936,1793203970}andregistry.access.redhat.com/ubi9/podman:1793203970. The previous build 9.8-1793032728 (sha256:2cfaa836…) also hadregistry.access.redhat.com/ubi9/podman:{latest,9.8,9.8-1793032728}. CentOS Stream 10's/usr/share/containers/policy.jsonrequiressigstoreSigned(Red Hat release3 key + Rekor) for registry.access.redhat.com with the defaultmatchRepoDigestOrExactidentity, so pulling:latestby tag on the upgraded guest is rejected. Fedora's policy and the composefs variants (which drop bound images) aren't affected.Reproduced with skopeo and the stock CentOS 10 policy/keys:
:latestis rejected;9.8-1793032728by tag and both builds by digest are accepted.This pins the previous build by digest everywhere the bound image is referenced. The storage check in
test-logically-bound-install.numatchedrepository:tag, which a digest reference lacks, so it now usespodman image existsper reference. Revert once Red Hat republishes the missing registry.access.redhat.com tag signatures.Generated-by: https://github.com/cgwalters/#llms