Bug 1554820
| Summary: | "dnf upgrade" reinstalls kernel packages reporting it cannot install best update candidate | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Lukas Ruzicka <lruzicka> | ||||
| Component: | dnf | Assignee: | Jaroslav Mracek <jmracek> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 28 | CC: | balay, dmach, gagbobada, jmracek, lruzicka, m.a.young, packaging-team-maint, rpm-software-management, vmukhame | ||||
| Target Milestone: | --- | Keywords: | Triaged | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | |||||||
| : | 1668256 (view as bug list) | Environment: | |||||
| Last Closed: | 2018-10-08 14:40:35 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Lukas Ruzicka
2018-03-13 12:37:12 UTC
Please can you provide data created by "dnf --debugsolver upgrade" command? Thanks a lot Additionally please can you try our upstream dnf if you can reproduce the bug (dnf copr enable rpmsoftwatemanagement/dnf-nightly)? Thanks a lot. I have the same issue, so I'll provide the debugdata from dnf (Sorry for all the copr related data, but I'm not sure I'm supposed to filter them out). I have the same F28Beta version of Fedora, and kernel keeps asking about reinstalling each time I run the upgrade command (with also a small issue about nss-pem package, it could show up in the debugdata). The copr doesn't work when I try to update dnf (even after correcting the small typo in rpmsoftwaremanagement name) Created attachment 1420271 [details]
debugdata folder created with --debugsolver
The requested data
It is related to modular support, and possibly libmodulemd. I saw it in a server updated from Boltron, which went away when I deleted the left over module yaml files. I recently replaced the install with a F28 server one, and the symptom has just reappeared after the latest update to dnf-2.7.5-9.fc28 which pulled in libmodulemd. Now dnf update gives Problem 1: cannot install both kernel-4.16.1-300.fc28.x86_64 and kernel-4.16.1-300.fc28.x86_64 - cannot install the best update candidate for package kernel-4.16.1-300.fc28.x86_64 - cannot install the best update candidate for package kernel-4.16.0-300.fc28.x86_64 Problem 2: cannot install both kernel-core-4.16.1-300.fc28.x86_64 and kernel-core-4.16.1-300.fc28.x86_64 - cannot install the best update candidate for package kernel-core-4.16.1-300.fc28.x86_64 - cannot install the best update candidate for package kernel-core-4.16.0-300.fc28.x86_64 Problem 3: cannot install both kernel-modules-4.16.1-300.fc28.x86_64 and kernel-modules-4.16.1-300.fc28.x86_64 - cannot install the best update candidate for package kernel-modules-4.16.1-300.fc28.x86_64 - cannot install the best update candidate for package kernel-modules-4.16.0-300.fc28.x86_64 ================================================================================ Package Arch Version Repository Size ================================================================================ Reinstalling: kernel x86_64 4.16.1-300.fc28 updates-testing 90 k kernel-core x86_64 4.16.1-300.fc28 updates-testing 24 M kernel-modules x86_64 4.16.1-300.fc28 updates-testing 27 M Transaction Summary ================================================================================ but dnf update --disablerepo=\*modular\* gives Nothing to do. as does dnf update --disablerepo=fedora-modular --disablerepo=updates-modular but the kernel reinstall happens if either fedora-modular or updates-modular is enabled. I see this issue when I invoke 'dnf update kernel*'. 'dnf update' does not list kernel in the update list. Its a bit disconcerting that it wants to reinstall currently running/active kernel [root@asterix ~]# dnf update kernel Last metadata expiration check: 0:00:00 ago on Sun 22 Apr 2018 11:52:22 AM CDT. Dependencies resolved. Problem: cannot install both kernel-4.16.3-300.fc28.x86_64 and kernel-4.16.3-300.fc28.x86_64 - cannot install the best update candidate for package kernel-4.16.3-300.fc28.x86_64 - cannot install the best update candidate for package kernel-4.16.2-300.fc28.x86_64 ============================================================================================== Package Arch Version Repository Size ============================================================================================== Reinstalling: kernel x86_64 4.16.3-300.fc28 updates-testing 91 k Transaction Summary ============================================================================================== Total download size: 91 k Is this ok [y/N]: n Operation aborted. [root@asterix ~]# uname -a Linux asterix 4.16.3-300.fc28.x86_64 #1 SMP Thu Apr 19 19:04:56 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux [root@asterix ~]# dnf update |grep kernel n Operation aborted. [root@asterix ~]# dnf check-update |grep kernel [root@asterix ~]# [root@asterix ~]# rpm -q dnf dnf-2.7.5-12.fc28.noarch [root@asterix ~]# The problem is fixed in upstream and will be released as part of dnf-4.0 and libsolv-0.6.35-3. Here is a copr repository for testing https://copr.fedorainfracloud.org/coprs/jmracek/dnf-upstream. *** This bug has been marked as a duplicate of bug 1616118 *** On F29 - I don't see this problem anymore [root@asterix ~]# rpm -q libsolv dnf libsolv-0.6.35-3.fc29.x86_64 dnf-3.6.1-1.fc29.noarch [root@asterix ~]# dnf update kernel* Last metadata expiration check: 0:03:27 ago on Mon 08 Oct 2018 09:50:00 AM CDT. Dependencies resolved. Nothing to do. Complete! [root@asterix ~]# I guess the fix is primarily in libsolv-0.6.35-3 and not necessarily in dnf-4.0 |