Bug 1141252 - Changing relative URL doesn't remove old URL.
Summary: Changing relative URL doesn't remove old URL.
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Pulp
Classification: Retired
Component: rpm-support
Version: 2.4.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: pulp-bugs
QA Contact: pulp-qe-list
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-12 14:19 UTC by akegata
Modified: 2015-02-28 22:19 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-28 22:19:30 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Pulp Redmine 522 0 None None None Never

Description akegata 2014-09-12 14:19:36 UTC 
Description of problem:
If a repo is published over http/https and the relative URL is later changed and the repo republished, the old relative URL still exists (although not everything published it still there, seems like only the listing files and the folders are left).

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

How reproducible:
Easily

Steps to Reproduce:
1. Create repo with relative URL RHEL 
2. pulp-admin rpm repo publish run --repo-id RHEL
3. pulp-admin rpm repo update --relative-url RedHat --repo-id RHEL
4. pulp-admin rpm repo publish run --repo-id RHEL
5. Check the available folders at <server>/pulp/repos

Actual results:
Both folders RHEL and RedHat exist.

Expected results:
Only the RedHat folder should remain.

Additional info:
Comment 1 Brian Bouterse 2015-02-28 22:19:30 UTC 
Moved to https://pulp.plan.io/issues/522
Note You need to log in before you can comment on or make changes to this bug.