Project

Profile

Help

Issue #434

Need a better validation for repo relative path

Added by skarmark@redhat.com over 6 years ago. Updated over 1 year ago.

Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
1. Low
Version:
2.4 Beta
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

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.

+ This bug was cloned from Bugzilla Bug #1100010 +

de0f36039fa63ee8a7e80e65fa593404 (6.22 KB) de0f36039fa63ee8a7e80e65fa593404 skarmark@redhat.com, 02/28/2015 11:06 PM

History

#1 Updated by bmbouter over 2 years ago

  • Status changed from NEW to CLOSED - WONTFIX

#2 Updated by bmbouter over 2 years ago

  • Severity set to 1. Low

Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.

#3 Updated by bmbouter over 2 years ago

  • Tags Pulp 2 added

#4 Updated by bmbouter over 1 year ago

  • Category deleted (14)

We are removing the 'API' category per open floor discussion June 16, 2020.

Please register to edit this issue

Also available in: Atom PDF