Bug 699891

Summary: WISHLIST: Allow specification of ks log file destination.
Product: Red Hat Satellite 5 Reporter: David Barr <dafydd>
Component: ProvisioningAssignee: Tomas Lestach <tlestach>
Status: CLOSED DEFERRED QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 540Keywords: FutureFeature
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-09-11 15:02:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 260381    

Description David Barr 2011-04-26 20:21:18 UTC 
+++ Description of problem:
Please update the kickstart configuration managers to allow specification of a path to the log files.

I have several RHNS-managed kickstart configurations. One %post script stopped working. I had trouble figuring out why. Part of my problem was that, after reboot, I could no longer see the output log file.

When %post script logging is selected, the scripts go in /root/<logfile>, as distinct from /mnt/sysimage/root/<logfile>. This means those log files are destroyed on reboot. Once I dropped the "reboot" keyword, I could go into /root and examine the logs.

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

+++ How reproducible:
Every time. I think this is normal behavior.

+++ Steps to Reproduce:
1. Boot from a kickstart file containing neither "shutdown" nor "reboot" keywords.
2. Compare the contents of /root and /mnt/sysimage/root
3. Note that files in /root are not expected to survive a reboot.
  
+++ Actual results:
Log files are saved in an unpreserved directory.

+++ Expected results:
Allow users to put the log files somewhere on sysimage.

+++ Additional info:

Thanks for an amazing product!