Red Hat Bugzilla – Bug 237203
RFE yum - Add feature to keep specific/failsafe version of kernel
Last modified: 2014-01-21 17:57:48 EST
Description of problem:
When yum updates the kernel if the number installed exceeds the "tokeep" limit
the oldest version is removed. I would like yum to be enhanced and a parameter
added to installonlyn.conf, e.g. "failsafe", such that the version specified by
"failsafe" will not be removed each time an update occurs.
Why do I want this?
1. Newer kernel updates do not always work. I want a known good/working kernel
resident on the system that can be booted using GRUB regardless of the number of
2. Keeping an rpm of the "failsafe" version on disk is not very efficient. For
example, if the new updated kernel fails to boot the system and a bootable
kernel is not in the GRUB menu you have to dig out the rescue or install CD and
then go about repairing the system.
3. With the new feature there would be no need have to track whether an update
will remove the "failsafe" kernel.
The kernel you're running and doing updates with is always going to be good
enough to get other kernels (otherwise, how did you get the one you're running)
hence the behavior of installonlyn.
If you want more substantial pinning support, there's a plugin in yum-utils to
The ability to fetch and install another kernel may be good enough for a
developer. I believe end users would like the ability to do more than that while
waiting for the next patch.
Are you referring to versionlock? There does not seem to be much about
versionlock on the Duke site other than a brief description. Is more
documentation available? I don't believe that it does what I want performed. I
want to be able to update the kernel using yum without having to be concerned
about the installonlyn plugin removing a particular kernel. It would also be
nice if the "tokeep" feature included the specified version in its count.
Upon further consideration I believe the "wontfix" and closing this RFE is
correct decision. It is, indeed, not a installonlyn bug. The bug was the default
inclusion of the installonlyn plugin as part of the FC installation process. For
a system administrator the proper course of action is to remove plugin.