Bug 969051 - RPM files with non-standard names are not handled properly
Summary: RPM files with non-standard names are not handled properly
Keywords:
Status: CLOSED DUPLICATE of bug 1101168
Alias: None
Product: Pulp
Classification: Retired
Component: user-experience
Version: 2.1.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: pulp-bugs
QA Contact: Preethi Thomas
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-30 14:44 UTC by James Findley
Modified: 2014-09-23 00:12 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-09-23 00:12:24 UTC
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.