Red Hat Bugzilla – Bug 851323
anaconda tries to poke /etc/chrony.conf at the end of install even if chrony wasn't in the installed package set
Last modified: 2012-09-05 20:53:29 EDT
I did a minimal install of F18 Alpha pre-TC4 (tflink's test build). At the very end of install, after bootloader installation had been done, the installer black screened, and in /tmp I found a traceback with this error from pyanaconda/ntp.py:
'cannot open config file /mnt/sysimage/etc/chrony.conf for reading (no such file or directory)'
(re-typed, probably not exact)
It seems anaconda tries to poke chrony.conf even if chrony wasn't in the installed package set. The installed system does actually boot okay - this must be one of the very last things anaconda does - and I verified that chrony wasn't installed. It may be a bug that chrony isn't in the minimal package set, but anaconda shouldn't really barf if it's not in the install.
Patch that should resolve this issues sent to anaconda-patches list.
Discussed at 2012-08-27 QA meeting, functioning as an NTH review meeting. Accepted as NTH as the crash obviously looks bad, and there are a few things that should be done after the crash which of course don't happen, like the copying of logs to the installed system.
anaconda-18.6.5-1.fc18 has been submitted as an update for Fedora 18.
anaconda-18.6.5-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.