Bug 1386251

Summary: Second installation on UEFI system creates grub2.cfg with linux instead of linuxefi for previous entry
Product: Red Hat Enterprise Linux 7 Reporter: Marek Hruscak <mhruscak>
Component: grub2Assignee: Peter Jones <pjones>
Status: CLOSED WONTFIX QA Contact: Release Test Team <release-test-team>
Severity: low Docs Contact:
Priority: medium    
Version: 7.4   
Target Milestone: rc   
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: 2020-12-15 07:47:17 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:
Bug Depends On:    
Bug Blocks: 1256306    
Attachments:
Description Flags
grub2-efi.cfg none

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.