Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionBrad Buckingham
2019-06-04 16:07:35 UTC
"puppet-foreman_proxy_content/PR 181":https://github.com/theforeman/puppet-foreman_proxy_content/pull/181 which is in response to #24316 has caused unintended problems.
GPG urls returned by candlepin in `/rhsm/consumers/<id>` contain "../../katello/api/repositories/<id>/gpg_key_content". When retrieving these directly from a katello server there is no problem. Trying to retrieve the URL using a smart proxy as a reverse proxy fails because of PR 181.
https://katello.example.net/katello/api/repositories/<id>/gpg_key_content = HTTP 200
https://katello-proxy.example.net/katello/api/repositories/<id>/gpg_key_content = HTTP 404
I would submit a PR but I do not what the plan is for the v1/v2 APIs going forward.
If v1/v2 should both remain supported then PR 181 should have added v2 URL support, not replaced v1. If the plan is to deprecate the v1 API then some other work has to be done. Candlepin seems to store the gpgUrl internally and any repo created pre (well I'm not sure which version exactly, but my repos were created in katello 3.4 and upgraded through to 3.9) will have to be updated from katello to candlepin. Rake task? Part of 30-upgrade.rb?
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-2019:3172