Red Hat Bugzilla – Bug 176704
installonlyn: fluctuating no of kernels present
Last modified: 2014-01-21 17:53:26 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.5) KHTML/3.5.0 (like Gecko)
Description of problem:
setting the onlyn to e.g 5 result in installation of 4 kernels. On
installation of the 5th every already installed kernel but the running kernel
I think this is due to the design of the break condition in the
postresolve_hook function in installonlyn.
The variable numleft will already be 0 before decrementing when on
installation of the last kernel of the preselected set size.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. set to_keep=4 (/etc/yum/pluginconf.d/installonlyn.conf)
2. install a kernel (no 1, in adition to the running kernel)
3. install a kernel (no 2)
4. install a kernel (no 3)
Actual Results: Only 2 kernels are installed (the running + the newest)
Expected Results: The preset to_keep number of kernels present: only the oldest dropped
when the "desired" count would have been exceeded.
reproducibility: this happens on istallation of every (n-1)'th kernel (with
to_keep=n) - if I got the arithmetic right.
*** Bug 176705 has been marked as a duplicate of this bug. ***
Bump. This bug is still present in yum-2.5.1-5 .
My /etc/yum/pluginconf.d/installonlyn.conf contains:
# this sets the number of package versions which are kept
Today's rawhide update would have wiped out all my backup kernels.
Package Arch Version Repository Size
kernel i686 2.6.15-1.1948_FC5 development 13 M
kernel-devel i686 2.6.15-1.1948_FC5 development 4.7 M
kernel i686 2.6.15-1.1928_FC5 installed 33 M
kernel i686 2.6.15-1.1917_FC5 installed 33 M
kernel i686 2.6.15-1.1915_FC5 installed 33 M
kernel-devel i686 2.6.15-1.1915_FC5 installed 14 M
kernel-devel i686 2.6.15-1.1917_FC5 installed 14 M
kernel-devel i686 2.6.15-1.1928_FC5 installed 13 M
Install 2 Package(s)
Update 113 Package(s)
Remove 6 Package(s)
Total download size: 189 M
Is this ok [y/N]: n
Exiting on user Command
Sorry, that "enabled=0" line should have read "enabled=1".
I cut 'n pasted the file that I modified to let yum run
the update without losing my kernels.
Hah, dumb bug. Fixed in CVS, will be in 2.5.3-2