grub.conf modified to boot old kernel when applied multiple kernel errata's from Satellite server

Solution Unverified - Updated -

Issue

  • Installing or updating kernel package(s) from Satellite does not modify grub.conf to make latest kernel to boot by default,

    • As example: After installing kernel 2.6.18-194.11.3.el5 on client system grub.conf entries are as below,
    # default=0  
default=0  
timeout=5  
splashimage=(hd0,0)/grub/splash.xpm.gz  
hiddenmenu  
title Red Hat Enterprise Linux Server (2.6.18-194.8.1.el5)  
 root (hd0,0)  
 kernel /vmlinuz-2.6.18-194.8.1.el5 ro root=/dev/rootvg/rootvol  
 initrd /initrd-2.6.18-194.8.1.el5.img  

title Red Hat Enterprise Linux Server (2.6.18-194.11.3.el5)  
 root (hd0,0)  
 kernel /vmlinuz-2.6.18-194.11.3.el5 ro root=/dev/rootvg/rootvol  
 initrd /initrd-2.6.18-194.11.3.el5.img  

title Red Hat Enterprise Linux Server (2.6.18-194.el5)  
 root (hd0,0)  
 kernel /vmlinuz-2.6.18-194.el5 ro root=/dev/rootvg/rootvol  
 initrd /initrd-2.6.18-194.el5.img

Environment

  • Red Hat Network Satellite 5
  • Red Hat Enterprise Linux

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.