Bug 851323

Summary:	anaconda tries to poke /etc/chrony.conf at the end of install even if chrony wasn't in the installed package set
Product:	[Fedora] Fedora	Reporter:	Adam Williamson <awilliam>
Component:	anaconda	Assignee:	Vratislav Podzimek <vpodzime>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	18	CC:	anaconda-maint-list, g.kaviyarasu, hamzy, jonathan, vanmeeuwen+fedora
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	AcceptedNTH
Fixed In Version:	anaconda-18.6.4-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	851653 (view as bug list)		Environment:
Last Closed:	2012-09-06 00:53:29 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:
Bug Depends On:
Bug Blocks:	752662, 846989, 851653

Description Adam Williamson 2012-08-23 19:19:54 UTC

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.

Comment 1 Vratislav Podzimek 2012-08-24 14:30:08 UTC

Patch that should resolve this issues sent to anaconda-patches list.

Comment 2 Adam Williamson 2012-08-27 17:02:45 UTC

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.

Comment 3 Fedora Update System 2012-09-01 05:11:50 UTC

anaconda-18.6.5-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/anaconda-18.6.5-1.fc18

Comment 4 Fedora Update System 2012-09-06 00:53:29 UTC

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.