Bug 497290 - Updating kernel does not update grub
Summary: Updating kernel does not update grub
Status: CLOSED DUPLICATE of bug 124246
Alias: None
Product: Fedora
Classification: Fedora
Component: mkinitrd
Version: rawhide
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2009-04-23 08:43 UTC by Phil
Modified: 2009-12-26 13:12 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2009-04-24 07:07:23 UTC
Type: ---

Attachments (Terms of Use)

Description Phil 2009-04-23 08:43:47 UTC
Description of problem:
every single kernel update i do does not update grub.  this issue persists through complete reinstalls.

Version-Release number of selected component (if applicable):
F11 rawhide

How reproducible:
without fail - or with fail depending on where you stand :).

Steps to Reproduce:
1. install x86_64 system
2. update kernel
3. inspect /boot/grub/grub.conf
Actual results:
additional kernel line has not been added to grub.conf

Expected results:
new kernel be listed to easily boot in to.

Additional info:
i can still boot the system to the new kernel by either manually updating grub.conf or using the grub command line.... ugh!

is this related to the system-config-boot issue?? bug #473798

Comment 1 Chuck Ebbert 2009-04-23 19:15:06 UTC
what happens if you manually run the new-kernel-pkg command?  e.g.

 new-kernel-pkg --depmod --install

Comment 2 Dave Jones 2009-04-23 19:53:59 UTC
the only time I saw something like this, /etc/grub.conf was a broken symlink, which caused /sbin/grubby to go nuts.

Comment 3 Phil 2009-04-23 21:33:58 UTC
Symlink's fine:
lrwxrwxrwx. 1 root root     11 2009-04-19 23:14 menu.lst -> ./grub.conf

[root@x64 grub]# new-kernel-pkg -v --depmod --install
initrdfile is /boot/initrd-
running depmod for
found /boot/initrd- and using it with grubby
adding to /boot/grub/grub.conf
grubby fatal error: unable to find a suitable template
/etc/lilo.conf does not exist, not running grubby

Comment 4 Dave Jones 2009-04-23 22:30:37 UTC
LILO !?!#@$!

reassigning to mkinitrd (the package which provides grubby)

Comment 5 Hans de Goede 2009-04-24 07:07:23 UTC
I'm afraid this is a known unknown (as in we don't know the cause) issue, marking this as a dup of the original bug.

Is there perhaps anything weird with your grub.conf ? Try copying over a grub.conf from another machine and do minimal editing to make it match the
machine in question. That might help. If that helps it would be nice if you could piecemeal warp the new grub.conf into the non working one to find out what breaks grubby.

*** This bug has been marked as a duplicate of bug 124246 ***

Note You need to log in before you can comment on or make changes to this bug.