Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.

Since BZ#1684701, the 05-pulp-https.conf had the ProxyPass directive updated to use the new /v2/ API path for GPG Keys

In some cases the 05-pulp-https.conf is getting properly updated, but registered clients are still getting the old URL for gpgkey=... in /etc/yum.repos.d/redhat.repo

Suraj Patil found that in these cases, the below API call is still returning the old URL for GPG Keys

# curl -k -X GET https://<Your satellite hostname>:8443/rhsm/consumers/<Consumer ID of the client system>/ -cacert /etc/rhsm/ca/katello-server-ca.pem  --cert /etc/pki/consumer/cert.pem --key /etc/pki/consumer/key.pem | python -m json.tool

.....
               "gpgUrl": "../../katello/api/repositories/1177/gpg_key_content",
.....

A PR was submitted and merged that adds a rake task to the installer to update gpgUrls during update: https://github.com/Katello/katello/pull/8103

Hi William,

The PR mentioned in comment 6 is being tracked with bug 1717069.  Should we close this bugzilla as a duplicate of that one?