Red Hat Bugzilla – Bug 1349314
Dnf autoremove removes kernel-modules-extra but dnf update reinstalls those kernel modules again.
Last modified: 2017-04-12 10:53:20 EDT
Description of problem:
When i run dnf autoremove, it removes kernel-modules-extra version 4.5.7-300.fc24.
When i run autoremove the exact same kernel modules get reinstalled again.
Version-Release number of selected component (if applicable): 1.1.9
On my machine, it happens every time.
Steps to Reproduce:
1. Run sudo dnf autoremove
2. Run sudo dnf update
It removes kernel-modules-extra while it probably shouldn't
It shouldn't remove kernel-modules-extra
This is on a fresh install of fedora 24
In the description the second autoremove should be dnf update, sorry.
Please run dnf autoremove with --debugsolver and attach debugdata directory and also then run dnf update with --debugsolver and also attach debugdata.
Please, can you provide additional information about:
What packages were in autoremove transaction?
What packages were in upgrade transaction?
If after upgrade the `dnf autoremove` command is run, remove it again kernel-modules-extra ?
Thank you very much for additional information.
Created attachment 1173196 [details]
Debugdata after running autoremove and update
I don't know if this is proper, if you need more, just ask.
Jaroslav, the only package in both autoremove and update is:
kernel-modules-extra x86_64 4.5.7-300.fc24 @updates 2.1 M
If i run dnf autoremove after running dnf update, it still tries to remove the kernel modules extra, it's an endless cycle of autoremove and update.
Dnf doesn't mark kernel-modules-extra-4.5.7-300 as userinstalled when it updates the kernel-modules-extra-4.5.5-300 package (which is userinstalled).
I seem to remember a fix in dnf or hawkey that makes it propagate the userinstalled flag on update, so maybe this is already solved. Or it does not work with multiinstall packages.
We will investigate. Thanks Michael for the hint.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Hello, i'm sorry if this is innapropriate, but this is marked as easyfix, but it's still not fixed. How come?
Still seeing this behavior on Fedora 24 with latest updates.
Now on F25.
Please can you try dnf-2.0 from our test repository (sudo dnf copr enable rpmsoftwaremanagement/dnf-nightly)? Thanks a lot
btw, I can reproduce this on my tablet on F25.
Currently this doesn't happen anymore on f25 with dnf 1.1.
My currently installed kernels are: (output of rpm -qa kernel
Please can you Igor investigate the issue, try it to reproduce with DNF 2.0 and provide as much as possible information to make it fixable.
I do have the same problem with the kernel-modules package. Right now it's kernel-modules-4.9.8-201.fc25.x86_64. On 4.9.7 i used `sudo dnf mark userinstalled kernel-modules` which i thought to be a general mark, and not pinned to the version.
I create patch that should fix the problem: https://github.com/rpm-software-management/dnf/pull/775
dnf-2.3.0-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-80f2c2bb64
dnf-2.3.0-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-80f2c2bb64
dnf-2.3.0-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.