Bug 704887 - When adding a post install script (non-chroot) to a kickstart, satellite interpretes "#"
Summary: When adding a post install script (non-chroot) to a kickstart, satellite inte...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Provisioning
Version: 540
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ---
Assignee: Tomas Lestach
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: 462714
TreeView+ depends on / blocked
 
Reported: 2011-05-15 18:59 UTC by Raul Mahiques
Modified: 2018-11-14 11:49 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-04 15:40:29 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Raul Mahiques 2011-05-15 18:59:15 UTC
Description of problem:
When adding a post install script (non-chroot) to a kickstart through the web interface, satellite interpretes the "#" as real comments therefore doesn't show them in the kickstart file.

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

How reproducible:
Add a post install script (non-chroot) using the web interface which contains "#".



Actual results:
The "#" and anything after them in the same line will not appear in the final kickstart file. Causing deployments to fail in some cases.
If you comment out the # ( \# ) they will appear correctly.

 Example
    Script:
    echo -e "something \n\t###### something else\n\t ####..."

    Kickstart output from satellite:
    echo -e "something \n\t

    Script:
    echo -e "something \n\t\#\#\#\#\#\# something else\n\t \#\#\#\#..."

    Kickstart output from satellite:
    echo -e "something \n\t###### something else\n\t ####..."


Expected results:
"#" are not interpreted.

 Example
    Script:
    echo -e "something \n\t###### something else\n\t ####..."

    Kickstart output from satellite:
    echo -e "something \n\t###### something else\n\t ####..."

Comment 2 Tomas Lestach 2016-02-04 15:40:29 UTC
We have re-reviewed this bug, as part of an ongoing effort to improve  Satellite/Proxy feature and bug updates, review and backlog.

We believe this bug has been fixed in the latest Satellite 5 version (5.7), so closing the bug as CURRENTRELEASE. Please feel free to re-open in case you discover any issues.

Tomas and Xixi


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