Fedora Account System
Red Hat Associate
Red Hat Customer
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:
What command did you use when upgrading? I'm specifically interested in whether or not you used an --instrepo arg.
--instrepo was not used.
(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.
This comment was flagged a spam, view the edit history to see the original text if required.
I've also reproduced this when using --instrepo on Apple EFI hardware. tflink I think also has reproduced this on UEFI. Reopening.
Pretty sure this is actually fixed. Reopen if I'm wrong.