grub.cfg not updated during preupgrade

[jarmo]

Mon, 04 Jun 2012 08:19:42 -0430
Patrick O'Callaghan <pocallaghan at gmail.com> kirjoitti:

> I recently upgraded F16->F17 using preupgrade. I booted into F17 and
> everything seemed to work until I tried rebooting, whereupon I got a
> Kernel panic with a lot of stuff about missing files (mdadm, sh,
> cat, ...) and a panic backtrace. This was completely reproducible.
> 
> I then noticed that the running kernel was still
> kernel-3.3.7-1.fc16.x86_64, despite the fact that
> kernel-3.3.7-1.fc17.x86_64 had been installed by preupgrade, i.e.
> grub.cfg had not been changed to reflect the new kernel. I updated to
> F17 3.4 from updates-testing and the problem appears to have gone
> away, i.e. grub is now correct.
> 
> So it looks like the issue was that grub.cfg should have been changed
> during the preupgrade, but wasn't. Has anyone else seen this?
> 
> On a related note: how does one capture the console output when a
> panic like this occurs? It isn't in any log files (maybe by this time
> there isn't a filesystem) and it's a chore to have to copy it all by
> hand, which is why I haven't bothered in this case.
> 
> poc
> 

I have still this going, found this from bugzilla...

https://bugzilla.redhat.com/show_bug.cgi?id=789329

Two different comps, acting just same, with same output...

Jarmo