Plugins » Katello

I posted this here: https://community.theforeman.org/t/katello-4-1-2-1-404-error-through-content-proxy-due-to-incorrect-location-href/24812

It seems that for some reason the main server and the content proxy can use different schemas for the organization of the packages inside a repository which doesn't always seem to match.

Client accesses content proxy to retrieve the latest kibana rpm:

https://foreman-content.example.com/pulp/content/ORG/Production/centos7/custom/elastic/elasticsearch-6-x/Packages/k/kibana-6.8.18-x86_64.rpm

which results in a 404 for the client.

The content proxy uses the following URL to get the rpm from the main server:

https://foreman.example.com/pulp/content/ORG/Production/centos8/custom/elastic/elasticsearch-6-x/6.8.18/kibana-6.8.18-x86_64.rpm

which does not exist. The correct URL would be:

https://foreman.example.com/pulp/content/ORG/Production/centos8/custom/elastic/elasticsearch-6-x/Packages/k/kibana-6.8.18-x86_64.rpm