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):
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
additional kernel line has not been added to grub.conf
new kernel be listed to easily boot in to.
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
what happens if you manually run the new-kernel-pkg command? e.g.
new-kernel-pkg --depmod --install 18.104.22.168-102.fc11.x86_64
the only time I saw something like this, /etc/grub.conf was a broken symlink, which caused /sbin/grubby to go nuts.
lrwxrwxrwx. 1 root root 11 2009-04-19 23:14 menu.lst -> ./grub.conf
[root@x64 grub]# new-kernel-pkg -v --depmod --install 22.214.171.124-102.fc11.x86_64
initrdfile is /boot/initrd-126.96.36.199-102.fc11.x86_64.img
running depmod for 188.8.131.52-102.fc11.x86_64
found /boot/initrd-184.108.40.206-102.fc11.x86_64.img and using it with grubby
adding 220.127.116.11-102.fc11.x86_64 to /boot/grub/grub.conf
grubby fatal error: unable to find a suitable template
/etc/lilo.conf does not exist, not running grubby
reassigning to mkinitrd (the package which provides grubby)
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 ***