Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
c/image/docker.newImageSource, when using mirrors, creates an ImageReference with a types.ImageReference pointing at the mirror, with no record of the primary location. This breaks signature verification, which ultimately uses ImageSource.Reference() to decide what to verify the signature against.
(Affects all other c/image users in addition to Podman, notably including CRI-O.)
Assigning to Jindrich to verify per https://bugzilla.redhat.com/show_bug.cgi?id=1829061#c5
Matt, Miloslav and /or Jindrich, do you have an answer to Derrick's question about backporting to Podman v1.9? I know it will bin in v2.0
Test with podman-1.9.3-2.module+el8.2.1+6867+366c07d6.x86_64. The location will not be replaced by mirror references for policy part from debug log. So set this to verified.
Here is my registries.conf:
unqualified-search-registries = ['registry.access.redhat.com', 'registry.redhat.io', 'docker.io']
[[registry]]
prefix = "registry.access.redhat.com/ubi8"
insecure = true
blocked = false
location = "quay.io/ypu/test"
And here is the details:
# podman --log-level debug pull registry.access.redhat.com/ubi8
......
DEBU[0003] Using transport "docker" specific policy section registry.access.redhat.com
DEBU[0003] Requirement 0: denied, done
DEBU[0003] Error pulling image ref //registry.access.redhat.com/ubi8:latest: Source image rejected: A signature was required, but no signature exists
A signature was required, but no signature exists
ERRO[0003] error pulling image "registry.access.redhat.com/ubi8": unable to pull registry.access.redhat.com/ubi8: unable to pull image: Source image rejected: A signature was required, but no signature exists
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2020:3053