RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
I am attempting to configure a UEFI system with the /boot/efi partition on mdadm RAID 1. When I run grub2-install, I get this error:

grub2-install --target=x86_64-efi /dev/sda
Installing for x86_64-efi platform.
EFI variables are not supported on this system.
efibootmgr: option requires an argument -- 'd'
efibootmgr version 17
usage: efibootmgr [options]
...

bash-4.2# grep sda1 /proc/mdstat 
md1 : active raid1 sdb1[1] sda1[0]

Note that I used md 1.0 metadata, so the metadata should be at the end of the partition and not interfere with EFI booting.

Version-Release number of selected component (if applicable):
grub2-tools-2.02-0.80

How reproducible:
always

Steps to Reproduce:
1. Configure the ESP partition as a raid 1 FAT32 partition
2. Mount it as /boot/efi
3. run "grub2-install --target=x86_64-efi /dev/sda"

Actual results:
grub2-install --target=x86_64-efi /dev/sda
Installing for x86_64-efi platform.
EFI variables are not supported on this system.
efibootmgr: option requires an argument -- 'd'
efibootmgr version 17
usage: efibootmgr [options]
...

Expected results:
No error.

Additional info:

If I run these commands manually after grub2-install, the system boots OK:

efibootmgr -q -c -L 'CentOS (sda)' -d /dev/sda -p 1
efibootmgr -q -c -L 'CentOS (sdb)' -d /dev/sdb -p 1

Also, it seems wrong that grub2-install ignores the return status from efibootmtr.
The return code from grub_util_exec() is currently ignored.

So I guess that grub-core/osdep/unix/platform.c:grub_install_register_efi() needs
to be patched. 

This upstream bug has a patch to improve the error message, but that doesn't
really solve the problem:

https://savannah.gnu.org/bugs/?46805

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.