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.

Satellite 6 supports HTTP UEFI Boot provisioning for some time now, but there were some bugs in Grub2 bootloader which prevented from using that on RHEL7-based HTTPBOOT Capsule. This is now fixed and will be in future version of RHEL7, therefore we should make sure that those are documented.

The HTTP UEFI provisioning process is the same as PXE process, the only difference is that PXE loader must be set to "Grub2 UEFI" and a capsule with HTTPBoot feature must be associate with the provisioning subnet. Other than that, everything works out of box including Discovery.

QA NOTES:

To enable IPv6 UEFI you must create libvirt VM in UEFI mode, then hit ESC and enter EFI firmware TUI, change boot order to boot HTTP UEFI IPv4 as the first item.

When testing, make sure latest grub2 from 7.9 RHEL is installed before foreman-installer is executed.

The HTTP boot process on IPv6 has been tested using the guide that is a part of this PR: https://github.com/theforeman/foreman-documentation/pull/116/files

The IPv6 HTTP boot and provisioning works correctly, a host boots from the network, and is successfully kickstarted.

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.8 release), 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-2020:4366