Grub2 UEFI HTTP/HTTPS for CentOS/RedHat

Support
,
1

I know there are bootloaders available for Grub2 UEFI HTTP and HTTPS, I’ve tried to make use of this with CentOS 7 and 8 but the host form says manual configuration is required. I haven’t been able to figure out what manual configuration, is this something that is possible?

2

Hello and welcome to the community!

As a first step, can you take a look through this chapter in the provisioning docs: Provisioning Guide - it might just get you where you need to be!

Thanks,

Melanie

3

Thanks, I think I was reading an older version of that that didn’t cover that. My hope was I could use the Grub2 UEFI HTTP bootloader to prevent needing TFTP, that doesn’t seem possible if I’m reading correctly.

4

You are not reading correctly. That’s totally possible with recent version of Foreman/Katello.

https://docs.theforeman.org/nightly/Provisioning_Guide/index-foreman.html#creating-hosts-with-uefi-http-boot-provisioning_provisioning

5

That’s encouraging, but I don’t think I’m understanding. The guide you pointed me to seems to require:

–foreman-proxy-tftp true

I tried turning it off anyway, but then I just get an error saying ERF12-5472 [ProxyAPI::ProxyException]: Unable to set TFTP boot entry

6

How about trusting our documentation, is that so hard? :wink:

HTTP Boot feature actually requires TFTP feature to operate. If you cannot have TFTP service, just block it via firewall. But Foreman still needs to connect to the TFTP REST API to perform boot files management.

I’ve filed a docs PR to improve our HTTP Booting Requirements section.

7

Ah ok, that makes sense, thanks for clearing up my confusion

2 Likes
8

No problem, I am improving the docs so noone else hopefully run into this!

Thanks for the report, cheers.