Project

General

Profile

Bug #19366

Complex/Strange Upstream Yum URL Results In Incorrect Upstream Package URLs

Added by Jason Nance about 5 years ago. Updated almost 4 years ago.

Status:
Rejected
Priority:
Normal
Category:
Repositories
Target version:
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

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:

http://sw.centricgroup.com/Orion/AgentManagement/LinuxPackageRepository.ashx?path=/dists/centos-7/x86_64

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:

http://sw.centricgroup.com/Orion/AgentManagement/LinuxPackageRepository.ashx/swiagent-1.6.0.1647-756007-centos-7.1-x64.rpm

However, the correct path to the package is:

http://sw.centricgroup.com/Orion/AgentManagement/LinuxPackageRepository.ashx?path=/dists/centos-7/x86_64/swiagent-1.6.0.1647-756007-centos-7.1-x64.rpm

Using a yum configuration to hit the upstream repo directly works.

Primary.xml and repomd.xml from upstream attached.

Katello server is:

CentOS 7
Katello 3.2.2
Foreman 1.13.4
Pulp 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
4fad7d8494f906c08bd77dfcfe5237f1c2441d9dfb6d645d01532dfe3d63c393-primary.xml.gz 4fad7d8494f906c08bd77dfcfe5237f1c2441d9dfb6d645d01532dfe3d63c393-primary.xml.gz 1 KB upstream primary.xml Jason Nance, 04/24/2017 03:20 PM
repomd.xml repomd.xml 2.9 KB upstream repomd.xml Jason Nance, 04/24/2017 03:20 PM

History

#1 Updated by John Mitsch about 5 years ago

  • Legacy Backlogs Release (now unused) set to 114

#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 (114)

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?

Thanks

#3 Updated by Jason Nance about 5 years ago

Pulp issue 2748 opened: https://pulp.plan.io/issues/2748

#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.

Also available in: Atom PDF