Bug 1213043

Summary:	dnf autoremove wants to booted (most recent) kernel (4.0.0.1)
Product:	[Fedora] Fedora	Reporter:	Flo H. <emailtoflorian>
Component:	dnf	Assignee:	Packaging Maintenance Team <packaging-team-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	22	CC:	jsilhan, mluscon, mmraka, packaging-team-maint, pnemade, rholy, tim.lauridsen, vmukhame
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-04-20 06:33:13 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 Flo H. 2015-04-18 02:26:11 UTC

Description of problem:
dnf autoremove is intending to remove the current (most recent) booted kernel (4.0.0.1). Makes no sense.


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

0.6.5
  Installed: dnf-0:0.6.5-1.fc22.noarch at 2015-04-13 15:35
  Built    : Fedora Project at 2015-03-31 17:57

  Installed: rpm-0:4.12.0.1-9.fc22.x86_64 at 2015-04-16 14:42
  Built    : Fedora Project at 2015-04-15 09:21


How reproducible:
sudo dnf autoremove

Steps to Reproduce:
1.
2.
3.

Actual results:

$ sudo dnf autoremove 
Using metadata from Fri Apr 17 18:51:22 2015 (3:26:49 hours old)
Dependencies resolved.
Error: The operation would result in removing the booted kernel: kernel-core-4.0.0-1.fc22.x86_64.



Expected results:


Additional info:

Comment 1 Michael Mráka 2015-04-20 06:33:13 UTC


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

Comment 2 Flo H. 2015-09-12 11:29:39 UTC

Same happening again with kernel 4.1.6-201.fc22