Issues encountered upgrading with yum from Fedora 16 to Fedora 17

[Adam Williamson]

On Mon, 2012-04-02 at 11:24 -0400, Jonathan Kamens wrote:
> On 4/2/2012 3:38 AM, Adam Williamson wrote: 
> > On Sun, 2012-04-01 at 00:16 -0400, Jonathan Kamens wrote:
> > > After the upgrade, both named.service and dhcpd.service were disabled
> > > in systemd, even though they were both enabled prior to the upgrade.
> > > Perhaps this is because named and dhcpd were switched to systemd in
> > > F17? I imagine other people are going to run into this issue and be
> > > irritated by it. Note that the upgrading with yum page listed above
> > > mentions recording enabled services before the upgrade and restoring
> > > them afterward for the Fedora 15 -> Fedora 16 upgrade, but not for the
> > > Fedora 16 -> Fedora 17 upgrade. If some services are being converted
> > > from initscripts to systemd in F17, they need to be called out on this
> > > page.
> > Yes, this is just the same as F15->F16, we should probably just copy
> > that text into the F16->F17 section.
> I filed separate bug reports about named and dhcpd, and the dhcpd
> folks claim that dhcpd was not changed from init to systemd in F17.
> See https://bugzilla.redhat.com/show_bug.cgi?id=808890 .

Hum, that seems to be true. It seems to be systemd in both 16 and 17. So
I'm not sure why its default status would change on upgrade, unless
there's a bad script in the package.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net