Bug 808889

Summary:	named disabled after yum update from F16 to F17
Product:	[Fedora] Fedora	Reporter:	Jonathan Kamens <jik>
Component:	bind	Assignee:	Adam Tkac <atkac>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	17	CC:	atkac, ovasik
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-04-19 13:08:41 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jonathan Kamens 2012-04-01 14:41:13 UTC

The named service, which was enabled prior to the upgrade, was disabled after upgrading from F16 to F17 as per https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum.

I suspect this is because it was converted from initscripts to systemd.

The instructions at the URL referenced above say to check which services are enabled before upgrading to F16 and re-enable them afterward, but it doesn't say the same thing about upgrading to F17.

If there are services being converted from initscripts to systemd in F17, then either (a) they need to automatically save and restore their status during the upgrade, or (b) the instructions at the URL mentioned above need to explain how to preserve the status of those services when upgrading.

Comment 1 Adam Tkac 2012-04-19 13:08:41 UTC

Per http://lists.fedoraproject.org/pipermail/devel/2012-April/165917.html this kind of changes isn't documented, closing.

If you disagree and think that this should be documented somewhere, please reopen this bug.