Bug 2159778

Document URL: 

for Satellite 6.11:
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.11/html/provisioning_hosts/using_pxe_to_provision_hosts_provisioning#Creating_Hosts_with_UEFI_HTTP_Boot_Provisioning_provisioning

for Satellite 6.12:
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.12/html/provisioning_hosts/using_pxe_to_provision_hosts_provisioning#Creating_Hosts_with_UEFI_HTTP_Boot_Provisioning_provisioning

Section Number and Name: 

6.5. Creating Hosts with UEFI HTTP Boot Provisioning

Describe the issue: 

As a result of the UEFI fixes for VMware (see bz #s 2112436, 2122180 and 2112436, as well as the following foreman bug from which those bugzillas derive), UEFI provisioning defaults to the grub entry "print warning and power off".

foreman bug:  https://projects.theforeman.org/issues/34532


Suggestions for improvement: 


One workaround is to manually select another menu option.

Another workaround re-enables normal UEFI provisioning in VMware:

> In Satellite UI --> Administer --> Settings --> Provisioning --> The value of "Default PXE local template entry" is empty by default but you want to ensure that once the system goes for final reboot, it boots from HDD directly i.e. via OS but not network.  To do this, set "force_local_chain_hd0" as the value of that option.


We would like to incorporate these workarounds into our provisioning documentation to better serve our customers.



Additional information: 

Without a workaround, UEFI provisioning on VMware loses its automated character, becoming a manual process.