Hide Forgot
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 ####..."
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