Bug 1386251 - Second installation on UEFI system creates grub2.cfg with linux instead of linuxefi for previous entry
Summary: Second installation on UEFI system creates grub2.cfg with linux instead of li...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: grub2
Version: 7.4
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: rc
: ---
Assignee: Peter Jones
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks: 1256306
TreeView+ depends on / blocked
 
Reported: 2016-10-18 13:40 UTC by Marek Hruscak
Modified: 2020-12-15 07:47 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-15 07:47:17 UTC
Target Upstream Version:


Attachments (Terms of Use)
grub2-efi.cfg (6.12 KB, text/plain)
2016-10-18 13:40 UTC, Marek Hruscak
no flags Details

Description Marek Hruscak 2016-10-18 13:40:01 UTC
Created attachment 1211744 [details]
grub2-efi.cfg

Description of problem:
I had installation of RHEL-7.x on UEFI system and trying to install different installation, system is installed and bootable.
But /boot/efi/EFI/redhat/grub.cfg for previous version contains linux and initrd instead of linuxefi and initrdefi, which makes OS unbootable on first look.

Version-Release number of selected component (if applicable):
RHEL-7.x

How reproducible:
Always

Steps to Reproduce:
1. install e.g. RHEL-7.3-Beta on UEFI system, use default partitioning but leave some free space for next installation
2. make second(may be same version) installation on remaining space 
3. reboot
4. try to select and boot previous system from boot menu

Actual results:
Menu entry for previous system is contain wrong command

Expected results:
Previous system should be bootable using menuentry from grub2.cfg

Additional info:
Easy workaround:
Add suffix efi to linux and initrd in grub2 menu, then boot

similar on Fedora: bug 1350138

Comment 2 RHEL Program Management 2020-12-15 07:47:17 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.


Note You need to log in before you can comment on or make changes to this bug.