Bug 862442

Summary: kickstart script files are lost after reboot
Product: [Fedora] Fedora Reporter: Jesse Keating <jkeating>
Component: anacondaAssignee: David Cantrell <dcantrell>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: clumens, dcantrell, g.kaviyarasu, jonathan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: anaconda-18.13 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-10-16 17:50:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jesse Keating 2012-10-02 22:41:46 UTC 
When kickstart scripts don't use --logfile, they get written to /tmp/  either outside the chroot or inside.  When done outside the chroot they are lost upon reboot.  When done inside the chroot they are written to /tmp/ which is tmpfs and thus lost on reboot.

They need to be written elsewhere, and copied to /var/log/anaconda/ on the installed system.  However the facility to copy the logs is itself a kickstart script, chicken/egg.

We can always write out the log file to the out of chroot location of /tmp/ but we need a better solution for copying them in.
Comment 1 Jesse Keating 2012-10-02 22:45:46 UTC 
Maybe the ks script that copies the logs can use a --logfile option, and we'd just hardcode that to /mnt/sysimage/<somewhere>.  That seems dangerous.  Or we can just not worry about the log messages from this file?