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.
+++ This bug was initially created as a clone of Bug #2184640 +++
Description of problem:
> the same issue seems to happen when checking the container image
> signature from a centos-9 host, we reported here:
> https://bugs.launchpad.net/tripleo/+bug/2015309
Follow up on that, when verifying container signatures, keys are configured per registry in /etc/containers/policy.json
for registry.access.redhat.com/ubi9:latest in the failing CI job, the key is /etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release provided by containers-common on CS9
which was not updated yet:
# curl https://gitlab.com/redhat/centos-stream/rpms/containers-common/-/raw/c9s/RPM-GPG-KEY-redhat-release | gpg2 --list-packets
# off=0 ctb=99 tag=6 hlen=3 plen=525
:public key packet:
version 4, algo 1, created 1256212795, expires 0
pkey[0]: [4096 bits]
pkey[1]: [17 bits]
keyid: 199E2F91FD431D51
# off=528 ctb=b4 tag=13 hlen=2 plen=51
:user ID packet: "Red Hat, Inc. (release key 2) <security>"
# off=581 ctb=89 tag=2 hlen=3 plen=566
:signature packet: algo 1, keyid 199E2F91FD431D51
version 4, created 1256212795, md5len 0, sigclass 0x13
digest algo 2, begin of digest 6c e9
hashed subpkt 2 len 4 (sig created 2009-10-22)
hashed subpkt 27 len 1 (key flags: 03)
hashed subpkt 11 len 5 (pref-sym-algos: 9 8 7 3 2)
hashed subpkt 21 len 3 (pref-hash-algos: 2 8 3)
hashed subpkt 22 len 3 (pref-zip-algos: 2 3 1)
hashed subpkt 30 len 1 (features: 01)
hashed subpkt 23 len 1 (keyserver preferences: 80)
subpkt 16 len 8 (issuer key ID 199E2F91FD431D51)
data: [4095 bits]
digest algo 2 = SHA-1 https://www.rfc-editor.org/rfc/rfc4880#section-9.4
SHA-1 was removed in gnup2-2.3.3-3.el9 for bug 2070722
Please update RPM-GPG-KEY-redhat-* keys provided by containers-common package in CS9.
Comment 2RHEL Program Management
2023-09-11 21:20:37 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 3RHEL Program Management
2023-09-11 21:21:59 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.