Bug 670828 - webui error - Configuration file path names must start with a '/'
Summary: webui error - Configuration file path names must start with a '/'
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Configuration Management
Version: 540
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Tomas Lestach
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: 462714
TreeView+ depends on / blocked
 
Reported: 2011-01-19 13:43 UTC by Jiri Kastner
Modified: 2014-07-04 13:23 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-07-04 13:23:59 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Jiri Kastner 2011-01-19 13:43:48 UTC
Description of problem:
when link is created using webui and starts with slash, there is no problem. while trying to reproduce bug 644985 i changed link target in configuration folder, to be relative using 'ln -snf target link' and change link uploaded back to channel. then i went to configuration webui and wanted to change selinux context and found, that using webui, i can create only absolute links, not relative, which to me sounds very dangerous, because if you need to deploy someting which will be chrooted, those links will be broken.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. follow comment 5 for bug 644985
2. before step 3. on that comment, go to folder, where link and file is stored
3. run 'ln -snf config.cfg{,.ln}
4. upload file back to satellite
5. go to webui and check 'Symbolic Link Target Filename/Path' value
6. value is not starting with slash, is relative
7. try change selinux context or target filename
8. click on 'update configuration file'
9. webui shows red allert saying, that path must start with slash
  
Actual results:
red alert

Expected results:
no red allert, as rhncfg can handle relative links

Additional info:


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