Bug 969051

Summary:	RPM files with non-standard names are not handled properly
Product:	[Retired] Pulp	Reporter:	James Findley <james.findley>
Component:	user-experience	Assignee:	pulp-bugs
Status:	CLOSED DUPLICATE	QA Contact:	Preethi Thomas <pthomas>
Severity:	high	Docs Contact:
Priority:	high
Version:	2.1.1	CC:	cduryee, mhrivnak, rbarlow, skarmark
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-09-23 00:12:24 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description James Findley 2013-05-30 14:44:21 UTC

Description of problem:

If the RPM has a name that doesn't match the expected name-version-release.arch.rpm naming scheme, pulp does not handle this properly.

The file is uploaded, and metadata is generated, but the href points to name-version-release.arch.rpm not the actual RPM name

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. rename an rpm file to name-version.arch.rpm
2. upload to pulp
3. attempt to install the file on a client

Actual results:

Yum cannot download the RPM


Expected results:

Yum downloads and installs the RPM

Additional info:

Comment 1 Chris Duryee 2014-09-23 00:12:24 UTC

I believe this was fixed as part of bz 1101168. If you still run into this issue in the latest release of pulp, please re-open this bug.

*** This bug has been marked as a duplicate of bug 1101168 ***