$ dnf distro-sync $ rpm -qa kernel kernel-4.0.6-300.fc22.x86_64 kernel-4.1.4-200.fc22.x86_64 kernel-4.2.0-0.rc5.git0.2.fc23.x86_64 reboot, select kernel that's not the latest $ uname -r 4.0.6-300.fc22.x86_64 $ dnf distro-sync --allowerasing Error: The operation would result in removing the booted kernel: kernel-core-4.0.6-300.fc22.x86_64.
*** Bug 1255463 has been marked as a duplicate of this bug. ***
(This is in reply to https://bugzilla.redhat.com/show_bug.cgi?id=1255463#c1 : Removing the oldest doesn't necessarily make sense for distro-sync. There may not even be a kernel upgrade happening. Probably you first want to see which old kernels are being removed because they are no longer in any repos (while keeping stuff associated with the running kernel such as -core, -modules and -modules-extra) and then see if you still need to remove some to keep within the install limit.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Still valid dnf-2.0.0-0.rc1.4.fc26.noarch.
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'.
I am sorry but I cannot reproduce it with dnf-2.3.0-1 and libdnf-0.8.1-1
I think that with this patch (https://github.com/rpm-software-management/libdnf/pull/285) dnf will work like Swiss ... :-) .