CentOS kernel update problem

Posted January 11, 2014 4.2k views
I'm fighting a losing battle on all my CentOS droplets to update the Kernel. I've noticed that although yum update is pulling down new versions, the grub.conf isn't getting updated. During the update, yum pukes a "grubby fatal error: unable to find a suitable template". The last version that did get updated into grub.conf was 2.6.32-358.6.2.el6.x86_64, back in October. All the droplets show the same contents for grub.conf, default=0 timeout=10 title vmlinuz-2.6.32-358.0.1.el6.x86_64 root (hd0,0) kernel /boot/vmlinuz-2.6.32-358.0.1.el6.x86_64 root=LABEL=root ro initrd /boot/initramfs-2.6.32-358.0.1.el6.x86_64.img That "root=LABEL=root" looks well dodgy to me? Anyway I've been experimenting on an "old" image, editing the grub.conf directly and then seeing if a "yum update" will take. So far, nothing I've done works. Sort of thing I've been trying is default=0 timeout=5 title CentOS (2.6.32-431.3.1.el6.x86_64) root (hd0,0) kernel /vmlinuz-2.6.32-431.3.1.el6.x86_64 ro LABEL=DOROOT initrd /initramfs-2.6.32-431.3.1.el6.x86_64 title CentOS Template Stanza root (hd0,0) kernel /vmlinuz-2.6.32-358.0.1.el6.x86_64 ro LABEL=DOROOT initrd /initramfs-2.6.32-358.0.1.el6.x86_64 as the LABEL=DOROOT showed up on a base CentOS droplet I created from your image. However, as I say, nothing works - all attempts keep hitting the same grubby error on the update. As another oddity, manually editing grub.conf and replacing the version with the latest one which update has pulled down (2.6.32-431.3.1.el6.x86_64) doen't actually seemt o change what gets booted! After a reboot, I'm still showing (e.g. a uname -r) as running 2.6.32-431.3.1.el6.x86_64! I'm not sure if this is related to the update problem, but Im all-round baffled and out of ideas! Anyone got any ideas before I raise it as a support ticket?

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Submit an Answer
2 answers
You're stuck using the kernels DO has listed in the control panel. Have to wait for them to update there before your droplet can use a newer one.
Ahhhhh thank you - light dawns. I had thought that that as they used KVM we would be able to update ourselves, but it seems not - have found a thread on that topic :/