Bug 893175

Summary:	fedup fails to clean up vmlinux-fedup and initramfs-fedup
Product:	[Fedora] Fedora	Reporter:	Chris Murphy <bugzilla>
Component:	fedup	Assignee:	Will Woods <wwoods>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	18	CC:	rdrijsen, tflink, wwoods
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-10-09 19:02:21 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 Chris Murphy 2013-01-08 19:41:58 UTC

Description of problem:
vmlinux-fedup and initramfs-fedup.img are left behind after a fedup ugprade; running grub2-mkconfig to create a current grub.cfg considers the fedup versions primary and boot by default.

Version-Release number of selected component (if applicable):
fedup-0.7.2-1.fc17

How reproducible:
always

Steps to Reproduce:
1. run fedup to completion.

  
Actual results:

These files are still present:
/boot/vmlinuz-fedup
/boot/initramfs-fedup.img

Expected results:

Those files should be removed as they're no longer needed, and interfere with the proper creation of grub.cfg with grub2-mkconfig.

Additional info:

Comment 1 Tim Flink 2013-01-08 21:12:10 UTC

What command did you use when upgrading? I'm specifically interested in whether or not you used an --instrepo arg.

Comment 2 Chris Murphy 2013-01-08 22:54:57 UTC

--instrepo was not used.

Comment 3 Tim Flink 2013-01-09 00:11:53 UTC

(In reply to comment #2)
> --instrepo was not used.

OK, that's what I thought - that means you got the upgrade.img that was built for beta. The cleanup done at the end of the upgrade process has been updated since beta and doesn't leave the kernel/initrd pair in /boot or the 'System Upgrade' option in the grub menu anymore.

I've confirmed this with an upgrade but I'll leave it open if you'd like to verify.

Comment 4 Kenny G 2013-01-12 18:34:56 UTC Comment hidden (spam)

This comment was flagged a spam, view the edit history to see the original text if required.

Comment 5 Chris Murphy 2013-01-12 19:59:55 UTC

I've also reproduced this when using --instrepo on Apple EFI hardware. tflink I think also has reproduced this on UEFI. Reopening.

Comment 6 Will Woods 2013-10-09 19:02:21 UTC

Pretty sure this is actually fixed. Reopen if I'm wrong.