Hello, I have just installed CentOS 7 onto two servers and applied all the current patches. There are currently two kernels installed: # rpm -q kernel kernel-3.10.0-123.el7.x86_64 kernel-3.10.0-123.9.3.el7.x86_64 However, if I reboot the servers they both start up on the older kernel: # uname -r 3.10.0-123.el7.x86_64 I would have expected them to restart using kernel 3.10.0-123.9.3. I know I can manually select the kernel to use at boot time (from the grub2 menu), but, as with CentOS 6, I would have expected the servers to reboot using the latest kernel automatically. Has anyone else noticed this? Any ideas as to why it might be happening? Thanks, John. -- John Horne Tel: +44 (0)1752 587287 Plymouth University, UK
> Has anyone else noticed this? Any ideas as to why it might be happening?/etc/sysconfig/kernel
On Wed, 2014-12-03 at 17:15 +0000, Lars Hecking wrote:> > Has anyone else noticed this? Any ideas as to why it might be happening? > > /etc/sysconfig/kernel >Yes and no. The above file has not been changed and states that a new kernel should be the default. It seems this problem has already been reported as a bug to CentOS and up to RedHat: https://bugs.centos.org/view.php?id=7651 John. -- John Horne Tel: +44 (0)1752 587287 Plymouth University, UK
On 03/12/14 17:10, John Horne wrote:> Hello, > > I have just installed CentOS 7 onto two servers and applied all the > current patches. There are currently two kernels installed: > > # rpm -q kernel > kernel-3.10.0-123.el7.x86_64 > kernel-3.10.0-123.9.3.el7.x86_64 > > > However, if I reboot the servers they both start up on the older kernel: > > # uname -r > 3.10.0-123.el7.x86_64 > > I would have expected them to restart using kernel 3.10.0-123.9.3. > I know I can manually select the kernel to use at boot time (from the > grub2 menu), but, as with CentOS 6, I would have expected the servers to > reboot using the latest kernel automatically. > > Has anyone else noticed this? Any ideas as to why it might be happening? > > > > > Thanks, > > John. >Someone already pointed you to the upstream bug for this. Uninstalling the original release kernel (3.10.0-123.el7.x86_64) should provide a workaround as the rest of the kernels should then be sorted in the correct order.