Yum update on FC5 install new kernel but don't update grub.conf

[Paul Howarth]

On Wed, 2006-05-10 at 19:09 -0400, Jim Cornette wrote:
> Ambrogio wrote:
> > Il giorno mar, 09/05/2006 alle 07.47 +0200, Ambrogio ha scritto:
> > Ok, but noone talk about the first problem.
> > 
> > What is wrong is that
> > rpm -ivh kernel-2.6.16-1.2111_FC5.x86_64.rpm
> > kernel-devel-2.6.16-1.2111_FC5.x86_64.rpm
> > Preparing...                ###########################################
> > [100%]
> >         package kernel-devel-2.6.16-1.2111_FC5 is already installed
> >         package kernel-2.6.16-1.2111_FC5 is already installed
> > 
> > and 
> > 
> > rpm -e kernel-2.6.16-1.2111_FC5.x86_64.rpm
> > kernel-devel-2.6.16-1.2111_FC5.x86_64.rpm
> > error: package kernel-2.6.16-1.2111_FC5.x86_64.rpm is not installed
> > error: package kernel-devel-2.6.16-1.2111_FC5.x86_64.rpm is not installed
> > 
> > no solution about that?
> > I think is not a problem related to disk spaces because yum check for
> > space requirement.
> > 
> > Maybe a rpm database's corruption.
> > I can try with --force but I want to check other way before.
> > 
> > Bye
> >  Ambrogio
> > 
> 
> The problem seems to be related to %post scriptlets being halted while 
> the kernel is being installed. This problem with scriptlets not being 
> performed were caused by SELinux labeling being incorrect and 
> interfering with the unpacking and installing of the rpms.
> 
> In a root shell run 'setenforce 0' followed by rpm -ivh --replacefiles 
> --replacepkgs kernel-<version>.rpm
> 
> setenforce 0 puts SELinux into permissive mode which prevent problems 
> with SELinux interfering with the installation of rpms.
> 
> --replacefiles and --replacepkgs will overwrite the files and add files 
> to already installed rpms without the need to use force as an option.
> 
> If this hapens to be the reason, you need to relabel your filesystem for 
> SELinux or put init into permissive mode when installing rpms.

I've heard of this happening with yumex (which wasn't originally
labelled with the correct SELinux context type), but not with yum or
plain rpm.

Paul.