Hostname Option 12, length 20: ""ĭomain-Name Option 15, length 7: "mts.sys" NTP, Vendor-Option, Requested-IP, Lease-Time IEN-Name-Server, Domain-Name-Server, Hostname, BS Subnet-Mask, Time-Zone, Default-Gateway, Time-Server Packet capture on the Foreman-Proxy at the time in which the host is powered on: The Foreman-Proxy has the tftp, dhcp, Logs, and Templates features enabled. It should not be looking in a non-existent “/EFI/rocky/” directory.īoth Foreman and Foreman-Proxy are on 3.1.2 How do I get the host to request its “grub.cfg-MACADDRESS” file from the /grub2 directory?Īfter the host has pulled the grub2/grub圆4.efi from the foreman-proxy, it should then pull the “grub.cfg-MACADDRESS” file from the grub2 directory as well. However, that file is not found in that location under the tftpboot root directory on the foreman-proxy.įoreman creates the “grub.cfg-MACADDRESS” file and places it in the “/grub2” directory under the tftp root.
It then requests the “/EFI/rocky/grub.cfg-MACDDRESS” file over TFTP from the foreman-proxy.
It also successfully pulls the grub2/grub圆4.efi file over TFTP. Upon powering on the bare metal host, I can see that it properly obtains it’s IP address and next-server over DHCP. Therefore, I am stuck supporting a UEFI solution. This host’s BIOS does not provide a “Legacy BIOS” option for booting.
ARCH TFTP CLIENT INSTALL
I’m trying to provision and install Rocky 8.5 onto a bare metal host.
0 kommentar(er)
