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

Bug 654713

Summary: Repo Publishing link creation could see a conflict
Product: [Retired] Pulp Reporter: John Matthews <jmatthew>
Component: user-experienceAssignee: Pradeep Kilambi <pkilambi>
Status: CLOSED DUPLICATE QA Contact: Preethi Thomas <pthomas>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.0.0CC: jason.dobies, 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: 2011-12-09 20:05:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description John Matthews 2010-11-18 17:15:08 UTC 
Description of problem:
If two repos are synced and their 'relative_path' is similar, it's possible a conflict can result.

Example:
Repo_A relative_path = "linux/fedora/f14/os/"
Repo_B relative_path = "linux/fedora"

If the above 2 repos were synced, the published link would fail for Repo_B.  
Repo_B would attempt to create link a link at "/var/lib/pulp/published/repos/linux/fedora" pointing to "/var/lib/pulp/repos/linux/fedora"

Problem is that Repo_A already has a link at: "/var/lib/pulp/published/repos/linux/fedora/f14/os".

When Repo_B attempts to create it's link, it will see that "linux" is already a directory and will fail.
Comment 2 Pradeep Kilambi 2011-12-09 20:05:05 UTC 

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