Project

General

Profile

Bug #25823

Unable to retrieve gpg_keys through smart proxy

Added by Alan Evans 2 months ago. Updated 2 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

puppet-foreman_proxy_content/PR 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/&lt;id&gt;/gpg_key_content = HTTP 200
https://katello-proxy.example.net/katello/api/repositories/&lt;id&gt;/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?


Related issues

Related to Katello - Bug #24316: Smart proxy missing GPG key (ProxyPass missing)Closed

History

#1 Updated by Alan Evans 2 months ago

  • Description updated (diff)

#2 Updated by Andrew Kofink 2 months ago

  • Related to Bug #24316: Smart proxy missing GPG key (ProxyPass missing) added

#3 Updated by Andrew Kofink 2 months ago

  • Triaged changed from No to Yes
  • Target version set to Katello Backlog

Also available in: Atom PDF