Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
DescriptionJoniel Pasqualetto
2023-03-21 14:52:50 UTC
Description of problem:
Currently, package grub2-efi-x64 is only installed on Satellite/Capsule if the TFTP feature is enabled.
However, this package is important for the generation of bootdisks for EFI systems, which can be done without having TFTP.
I understand this is a design choice. Reporting the BZ so we can consider changing it and having the package installed all the time.
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Install a satellite server, don't enable TFTP.
2. Check the presence of the package grub2-efi-x64 (it won't be there, assuming the server where Satellite is installed is using BIOS)
Actual results:
Only install grub2-efi-x64 when we enable TFTP
Expected results:
Have the package grub2-efi-x64 installed at all times
Additional info:
Issues observed due to the lack of this package is linked to UEFI+SecureBoot usage. Boot disk image is created, but fails to boot on Secure Boot enabled systems.
Issue is that file /boot/efi/EFI/redhat/grubx64.efi is not present (because it's provided by the package in question). I'm not sure how the file grubx64.efi is created on those circumstances, but it lacks instructions to properly boot with SecureBoot.
Having the package grub2-efi-x64 installed manually, allow generated bootdisk images to boot with SecureBoot properly.
Enabling the tftp feature also solves the issue, however it may be desired for customer to not have tftp enabled and use only bootdisks.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Important: Satellite 6.14 security and bug fix update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2023:6818