Actions
Issue #2748
closed
Complex/Strange Upstream Yum URL Results In Incorrect Upstream Package URLs
Status:
CLOSED - NOTABUG
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:
Description
I have an "on demand" product repository with a URL of:
When a client attempts to pull a package from that product repository the Pulp server attempts to pull the package from upstream using:
However, the correct path to the package is:
Using a yum configuration to hit the upstream repo directly works.
Primary.xml and repomd.xml from upstream attached.
Pulp version is 2.9.3.
If it makes a difference, when these repos are configured directly on the client they are done so as follows:
/etc/yum.repos.d/swiagent-centos-7.mirrors:
[swiagent]
name=SolarWinds Agent
mirrorlist=file:///etc/yum.repos.d/swiagent-centos-7.mirrors
enabled=0
gpgcheck=0
/etc/yum.repos.d/swiagent-centos-7.mirrors:
http://sw.centricgroup.com/Orion/AgentManagement/LinuxPackageRepository.ashx?path=/dists/centos-7/$basearch
Files
Actions
.