Red Hat Bugzilla – Bug 476593
RFE"done entry in install.log
Last modified: 2009-01-07 12:16:53 EST
I have a problem with the install.log. Now this may seem picky, but it would have helped with with another issue. I had an install that was not finishing and because it was rebooting, I didn't realize that.
How about in the install.log an entry when the final processing starts and another when it ends and it is ready to reboot.
This is really a seperate "bug", but it was caused by bug 476372.
The anaconda.log file writes a line for every step of the install process, so you would definitely get a line in there once it starts doing postinstall configuration - things like writing out the bootloader, writing the anaconda-ks.cfg file, etc. Is there a specific reason you also need something written to install.log?
Well this has to do with another bug I reported, 476372. When you look at the install log at the end you can't figure out if the entire install was successful, or if there was an error what went to a retry/abort screen that then abort/rebooted when you didn't get to it in time. If the install has progressed to a certain point where the reboot produces a working system you don't know you had a problem.
Is the anaconda.log stored somewhere that is available after the process is over that I can check? That might fix the problem, but the reason for suggesting the install.log is that this is the only permanent record of the install that I know of.
Ah, I see the problem now. The log files are only copied over to the installed system at the end, if the installation completes. So you'd find /var/log/anaconda.log. However, install.log is written to /root as the install progresses. So it is possible to get partially written install.log files, but you'll never see the /var/log/anaconda.log unless the install worked.
I'll go ahead and add something in to the install.log.
The next build of anaconda will include a line written to install.log at the end of all package installation and upgrades.