Bug 1100010

Summary: Need a better validation for repo relative path
Product: [Retired] Pulp Reporter: Sayli Karmarkar <skarmark>
Component: API/integrationAssignee: pulp-bugs
Status: CLOSED UPSTREAM QA Contact: pulp-qe-list
Severity: unspecified Docs Contact:
Priority: medium    
Version: 2.4 BetaCC: cperry, jmatthew
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:06:50 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:
Attachments:
Description Flags
traceback during publish when repo relative path is an absolute path none

Description Sayli Karmarkar 2014-05-21 19:21:21 UTC
Created attachment 898094 [details]
traceback during publish when repo relative path is an absolute path

If a user specifies relative path as an absolute path, we don't actually append it to publish directories (and maybe some other places), resulting in errors during publish (see attachment). 

We need to either do a better validation of relative path specified by the user and make sure that it is not an absolute path or convert it internally to a relative path.

Comment 1 Brian Bouterse 2015-02-28 22:06:50 UTC
Moved to https://pulp.plan.io/issues/434