Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
This is a request for packaging to also install the grub efi files in a /usr location which is accessible by all users.
There are use cases for grubx64.efi beyond booting the machine it is installed on. Specifically serving grubx64.efi (and the shim) over tftp to a remote machine will make it possible to enable secure boot for baremetal provisioning in OpenStack Ironic by using (signed) grub network boot instead of iPXE.
Requiring root just to copy grubx64.efi into the /tftpboot directory constrains /tftpboot population to a privileged tool. This has drawbacks, for example when the shim package is updated.
> Requiring root just to copy grubx64.efi into the /tftpboot directory constrains /tftpboot population to a privileged tool. This has drawbacks, for example when the shim package is updated.
Root is not required. Just unpack the rpm cpio ball and get grubx64.efi from there.
Let me provide some more background for the requirements here.
openstack-ironic is aiming to improve the install experience by auto-populating the /tftpboot director on service startup. This directory needs ipxe, grub, shim images plus some template generated text files.
This leads to a solution which must be unprivileged, configuration driven, and distro agnostic. This means that running custom scripts which do rpm unpacking is not an option, and pulling a package from the network is *really* not an option.
Red Hat family is unique in distros, installing root-only readable files to /boot/efi:
SUSE: /usr/share/efi/x86_64/grub.efi
Debian/Ubuntu: /usr/lib/grub/x86_64-efi-signed/grubnetx64.efi.signed
I'm fine with doing the packaging work to make this happen:
https://gitlab.com/redhat/centos-stream/rpms/grub2/-/merge_requests/19
Comment 6RHEL Program Management
2023-07-13 07:31:54 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.