Bug 1769632

Summary: dnf autoremove fails with Problem: The operation would result in removing the following protected packages: kernel-core
Product: [Fedora] Fedora Reporter: uor3ee
Component: dnfAssignee: Jaroslav Mracek <jmracek>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 31CC: dmach, jmracek, jrohel, mblaha, mhatina, packaging-team-maint, pkratoch, 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: Environment:
Last Closed: 2019-11-11 13:16:41 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:

Description uor3ee 2019-11-07 04:11:55 UTC
Description of problem:

After initial install from iso, kernel, kernel-modules, and kernel-modules-extra are all marked as userinstalled. But after pulling in the new kernel through dnf upgrade, no kernel packages are marked as userinstalled.

Running dnf autoremove gives Error: 
 Problem: The operation would result in removing the following protected packages: kernel-core


Version-Release number of selected component (if applicable): 4.2.9-5.fc31


How reproducible:

Brand new install of Fedora 31, upgrade adding a new kernel in addition to the one with the release, run dnf autoremove.


Steps to Reproduce:
1. Install Fedora 31
2. Run dnf upgrade to update system, bringing in a new kernel
3. Run dnf autoremove

Actual results:

Fails with Problem: The operation would result in removing the following protected packages: kernel-core


Expected results:

Provides an option to remove packages no longer needed.

Additional info:

Comment 1 Pavla Kratochvilova 2019-11-11 13:16:41 UTC

*** This bug has been marked as a duplicate of bug 1769788 ***