Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1141252

Summary:	Changing relative URL doesn't remove old URL.
Product:	[Retired] Pulp	Reporter:	akegata
Component:	rpm-support	Assignee:	pulp-bugs
Status:	CLOSED UPSTREAM	QA Contact:	pulp-qe-list
Severity:	medium	Docs Contact:
Priority:	medium
Version:	2.4.0	CC:	cduryee, ipanova, justin.garrison, mhrivnak
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:	2015-02-28 22:19:30 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 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