Red Hat Bugzilla – Bug 242909
Grub not updated properly on FC6 to F7 upgrade with xen kernels
Last modified: 2008-06-16 21:27:25 EDT
Description of problem:
On an upgrade to F7 from FC6, if the xen kernel is installed (and listed first
in grub.conf) then after the upgrade, the FC6 xen kernel is still listed and a
reboot fails. You must either edit grub manually or reboot and select the
correct kernel from the menu.
Version-Release number of selected component (if applicable):
Happened on both systems with xen and FC6 upgraded to F7.
Steps to Reproduce:
1.install Xen on FC6 system
2.upgrade to F7
3.reboot -- fails
Expected grub to be updated properly to remove the previous version xen kernel
(at the very least move it down in boot priority).
Should be able to reboot into latest xen kernel automatically from grub without
manual editing or selecting from menu.
I just got around to do several upgrades from FC6 to F7 at home on my i386
systems (intel p4's) and one of my AMD Athlon 64 boxes. In each case, and
WITHOUT any xen kernels ever installed on those systems), grub failed to update
properly and I had to remove the existing default boot option pointing to the
old FC6 kernel.
So, this isn't a problem with just xen kernels and upgrading. It seems to be
upgrading in general.
FWIW, I've got grub not updating kernels under xen on fc6 from 2.6.18 to 2.6.20.
#sudo /sbin/grub-install /dev/md0:
Installation finished. No error reported.
This is the contents of the device map /boot/grub/device.map.
Check if this is correct or not. If any of the lines is incorrect,
fix it and re-run the script `grub-install'.
# this device map was generated by anaconda
title Fedora Core (2.6.20-1.2948.fc6xen)
module /vmlinuz-2.6.20-1.2948.fc6xen ro root=/dev/md2
title Fedora Core (2.6.18-1.2869.fc6xen)
module /vmlinuz-2.6.18-1.2869.fc6xen ro root=/dev/md2
The grub screen doesn't show 2.6.20 when booting. SELinux is disabled.
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'.
Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.
Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:
The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 7 changed to end-of-life (EOL) status on June 13, 2008.
Fedora 7 is no longer maintained, which means that it will not
receive any further security or bug fix updates. As a result we
are closing this bug.
If you can reproduce this bug against a currently maintained version
of Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.