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.
Description of problem:
Microdnf is unable to retrieve gpg key on RHEL 8
Package installation on containers using the custom repository "Hashicorp" in RHEL 8 failed.
Version-Release number of selected component (if applicable):
How reproducible:
100%
Steps to Reproduce:
1) Log into the satellite web UI.
2) Create a content credential called "Hashicorp" of type "GPG Key" in Content-> Content Credentials; paste the "Hashicorp" public key from
https://rpm.releases.hashicorp.com/gpg
3) Create a product called "Custom" in Content -> Products
4) Create a repository on the Repositories tab called "Hashicorp", with type "yum",
Upstream URL "https://rpm.releases.hashicorp.com/RHEL/8/x86_64/stable" and GPG key
"Hashicorp"
5) Change the Download Policy to "On Demand".
6) Sync the repository by selecting it and clicking "Sync Now"
7) Create a content view "Test" and Add the "Hashicorp" repository to it on the Yum Content tab.
8) Click "Publish New Version" and wait for it to finish.
== Client Setup (RHEL-8) ==
1) Register the client host to the satellite server and attach the "Test" Content view on it.
2) Install podman on the RHEL 8 client host and Login to "registry.redhat.io".
# dnf install podman -y
# podman login registry.redhat.io
3) Pull the images from the registry hub.
# podman pull registry.redhat.io/ubi8/ubi-minimal
4) From there on, to reproduce the issue, install execute the following command:
# podman run --rm -it registry.redhat.io/ubi8/ubi-minimal microdnf --enablerepo=RedHat_Custom_Hashicorp install -y terraform
Actual results:
~~~
...
Downloading metadata...
Downloading metadata...
Package Repository Size
Installing:
...
Downloading packages...
error: package terraform-1.3.6-1.x86_64 cannot be verified and repo RedHat_Custom_Hashicorp is GPG enabled: /var/cache/yum/metadata/RedHat_Custom_Hashicorp-8-x86_64/packages/terraform-1.3.6-1.x86_64.rpm could not be verified.
/var/cache/yum/metadata/RedHat_Custom_Hashicorp-8-x86_64/packages/terraform-1.3.6-1.x86_64.rpm: digest: SIGNATURE: NOT OK
~~~
Expected results:
Package installation should be done without error.
Additional info:
1) This issue is not reproducible on "registry.redhat.io/ubi8/ubi" image.
2) This issue was hit on RHEL 7 product that is fixed via the following Bugzilla
Bug 1708628 - Microdnf unable to retrieve gpg key via http(s)
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 (librhsm bug fix and enhancement update), 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/RHBA-2023:3036