Bug 1813313

Summary:	[Tracker] Test HTTP UEFI on IPv6 (QA only tracker)
Product:	Red Hat Satellite	Reporter:	Lukas Zapletal <lzap>
Component:	Provisioning	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED ERRATA	QA Contact:	Radovan Drazny <rdrazny>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.8.0	CC:	inecas, sshtein
Target Milestone:	6.8.0	Keywords:	Triaged
Target Release:	Unused
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-10-27 13:00:52 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:
Embargoed:

Description Lukas Zapletal 2020-03-13 14:10:39 UTC

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.

Comment 4 Radovan Drazny 2020-10-13 14:45:30 UTC

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.

Comment 7 errata-xmlrpc 2020-10-27 13:00:52 UTC

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