Bug 1709927 - Content Hosts getting wrong gpgkey URL (i.e. not using /v2/ api)
Summary: Content Hosts getting wrong gpgkey URL (i.e. not using /v2/ api)
Keywords:
Status: CLOSED DUPLICATE of bug 1717069
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Credentials
Version: 6.4
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Perry Gagne
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-14 14:54 UTC by wclark
Modified: 2023-03-24 14:48 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-09-18 13:07:44 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github Katello katello pull 8103 0 None closed Fixes #25823 - Unable to retrieve GPG keys through smart proxy 2020-07-30 14:30:24 UTC

Description wclark 2019-05-14 14:54:52 UTC 
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",
.....
Comment 6 wclark 2019-05-16 13:41:48 UTC 
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
Comment 7 Brad Buckingham 2019-06-07 18:12:01 UTC 
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?
Note You need to log in before you can comment on or make changes to this bug.