Change example dnsmasq.conf in install doc for uefi
As described in https://bugs.launchpad.net/puppet-ironic/+bug/1714320, a loop can occur in which dnsmasq always indicates ipxe.efi as the bootfile if the client request has both UEFI and iPXE options set. This fixes the documentation for the example dnsmasq.conf so that loop won't occur. In addition, some UEFI clients use architecture type 9 so that is added to the example dnsmasq.conf. Related-Bug: 1714320 Change-Id: Icdefba2b1be47622c9bd9c3bfb9b3413964c9dac
This commit is contained in:
parent
b1c0656041
commit
25929f3d04
@ -302,8 +302,12 @@ nodes not supporting iPXE. To use iPXE, you'll need:
|
||||
dhcp-sequential-ip
|
||||
dhcp-match=ipxe,175
|
||||
dhcp-match=set:efi,option:client-arch,7
|
||||
dhcp-match=set:efi,option:client-arch,9
|
||||
# Client is already running iPXE; move to next stage of chainloading
|
||||
dhcp-boot=tag:ipxe,http://{IP}:8088/inspector.ipxe
|
||||
dhcp-boot=tag:efi,ipxe.efi
|
||||
# Client is PXE booting over EFI without iPXE ROM,
|
||||
# send EFI version of iPXE chainloader
|
||||
dhcp-boot=tag:efi,tag:!ipxe,ipxe.efi
|
||||
dhcp-boot=undionly.kpxe,localhost.localdomain,{IP}
|
||||
|
||||
First, we configure the same common parameters as with PXE. Then we define
|
||||
|
Loading…
Reference in New Issue
Block a user