Red Hat Bugzilla – Bug 198661
%post does not get logged to /root/ks-post.log anymore
Last modified: 2008-04-02 20:18:42 EDT
Description of problem:
Previous behavior logged all %post commands (custom & builtin). See
for an example.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create kickstart profile
2. Create a %post script
3. View kickstart and see if it is before or after the ") > /root/ks-post.log
Custom commands are after the ") > /root/ks-post" line which means the output of
custom scripts do not get logged.
Matt and I talked about this on irc and we decided:
Going to move this to 420 with the suggestion that we make it a configurable
option in the kickstart profile to log the post scripts.
This will allow customers to provision machines and execute actions in the post
section with possibly security related information and will allow them to decide
if they want the commands logged or not.
User firstname.lastname@example.org's account has been closed
We think this is fixed.
Custom commands are after the ") > /root/ks-post" line as mentioned in the bug.
checked in in rev 133524.
Note that this is a user configurable option. On the main kickstart details
page for each profile there is now a checkbox for "Log custom post scripts".
If enabled each post script is logged to /root/ks-post.log.
After creating a few custom scripts and enabling the option on the Kickstart
Details page, their output was logged, so I'm moving this bug to VERIFIED.
5.1 Sat GA so Closed for Current Release.