Bug 1100010 - Need a better validation for repo relative path
Summary: Need a better validation for repo relative path
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Pulp
Classification: Retired
Component: API/integration
Version: 2.4 Beta
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
: ---
Assignee: pulp-bugs
QA Contact: pulp-qe-list
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-21 19:21 UTC by Sayli Karmarkar
Modified: 2015-03-23 01:12 UTC (History)
2 users (show)

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


Attachments (Terms of Use)
traceback during publish when repo relative path is an absolute path (6.22 KB, text/plain)
2014-05-21 19:21 UTC, Sayli Karmarkar
no flags Details


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

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


Note You need to log in before you can comment on or make changes to this bug.