Complex/Strange Upstream Yum URL Results In Incorrect Upstream Package URLs
I think this may be a Pulp bug, but am starting here just in case. I'm more than happy to open this over there if appropriate.
I have a product repository with a URL of:
When a client attempts to pull a package from that product repository (via Katello content view) the Katello server attempts to pull the package using:
However, the correct path to the package is:
Using a yum configuration to hit the upstream repo directly works.
repomd.xml from upstream attached.
Katello server is:
If it makes a difference, when these repos are configured directly on the client they are done so as follows:
[swiagent] name=SolarWinds Agent mirrorlist=file:///etc/yum.repos.d/swiagent-centos-7.mirrors enabled=0 gpgcheck=0
#2 Updated by Justin Sherrill about 5 years ago
- Category set to Repositories
- Status changed from New to Need more information
- Assignee set to Justin Sherrill
- Legacy Backlogs Release (now unused) deleted (
I'm quite sure that this purely a behavior of pulp where they are chopping off the parameters from the URL. The fact that the initial on_demand sync is working (where no rpms are downloaded), affirms that we passed pulp the correct URL.
I could see an argument that these types of urls shouldn't' be supported, but i'll let the pulp team make that argument (or not). Can you open up a pulp issue on this matter?
#4 Updated by Justin Sherrill about 5 years ago
- Status changed from Need more information to Rejected
- Legacy Backlogs Release (now unused) set to 166
Thanks jason, I will go ahead and close this as i don't think there is anything for katello to do here. we can reopen if that turns out to not be the case.