Bug 1475874 - dnf upgrade does not remove old kernel although installonly_limit is exceeded
Summary: dnf upgrade does not remove old kernel although installonly_limit is exceeded
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf
Version: 26
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: rpm-software-management
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-27 14:00 UTC by k.c.harke
Modified: 2017-07-27 14:40 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-27 14:40:11 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description k.c.harke 2017-07-27 14:00:40 UTC
Description of problem:
In /etc/dnf/dnf.conf installonly_limit=2 is set. Nevertheless, 3 Kernel Versions are installed.

Version-Release number of selected component (if applicable):


How reproducible:
Set installonly_limit=2 in /etc/dnf/dnf.conf
sudo dnf upgrade

Steps to Reproduce:
1.
2.
3.

Actual results:
3 installed kernel versions

Expected results:
removing kernel-4.11.8-300 ....


Additional info:
dnf list | grep kernel ->
kernel.x86_64                          4.11.8-300.fc26                 @anaconda
kernel.x86_64                          4.11.10-300.fc26                @updates 
kernel.x86_64                          4.11.11-300.fc26                @updates

Comment 1 Jaroslav Mracek 2017-07-27 14:40:11 UTC
The oldest unbooted kernel will be removed only if in transaction will be the kernel. That means if there will be new kernel update available and you will update kernel, then instead of removal 1 kernel packages, two of them will be removed. The behavior was changed, because other users did not like, that if they install something, it also removes kernels over limit. Please if I did not understand well your problem, don't hesitate to reopen the bug report.


Note You need to log in before you can comment on or make changes to this bug.