another upgrade, another disaster

Adam Williamson awilliam at
Fri Jun 1 16:42:06 UTC 2012

On Fri, 2012-06-01 at 10:37 +0200, Caterpillar wrote:
> 2012/5/31 Adam Williamson <awilliam at> 
>         > Third bug: after preupgrade finished to download fc17
>         packages, I
>         > rebooted, but grub did not have a “upgrade system” entry. So
>         the
>         > computer is not upgradable with preupgrade.
>         Need more information.
> Could it be? 

No. In that comment I'm talking about what happens to the bootloader
once anaconda has fired up and started running the upgrade - what
anaconda does to the bootloader config. If you don't get an 'upgrade to
fedora 17' entry at all after preupgrade first stage, that's some kind
of bug in preupgrade itself: preupgrade has failed to modify the
existing bootloader config to add the entry.

>         No, that is not the case. See above. The issues with old
>         kernel sticking
>         around after upgrade were already known and reported before
>         release.
>         The #820351 case is fundamentally more or less impossible to
>         solve
>         entirely, outside of sticking Epochs in the kernel package. So
>         there was
>         no point holding up the release for that. The #820340 case is
>         specific
>         to preupgrade and isn't a showstopper, so we didn't hold the
>         release for
>         that one either. There is an upgrade currently in testing that
>         ought to
>         fix it.
> Please apologize me, but if #820340 was not a showstopper, so which
> bug should be a showstopper? I am very disappointed with that, because
> preupgrade is the official supported way to upgrade Fedora versions

It doesn't stop you from doing a successful upgrade. All it does is stop
you from shutting down cleanly, once.
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | adamwfedora

More information about the devel mailing list