mirror of
https://github.com/xcat2/xcat-core.git
synced 2026-11-21 18:02:18 +00:00
25720c77a7
dhcp6_bootfile_url_for_node writes RFC 5970 option 59 for grub2 alone, so a node with netboot=ipxe takes its reserved IPv6 address and has nothing to load. Its firmware then releases the address and solicits again. grub2 was the only loader an IPv6 node could use. The iPXE build xCAT ships does speak DHCPv6: snponly.efi, the UEFI loader of ipxe-xcat 2.0.0, carries dhcpv6, ipv6 and four IPv6 strings, against a control of 26 iPXE and dhcp strings in the same binary. The firmware that solicits over DHCPv6 is UEFI, so the UEFI loader is the only one such a client can ask for. An ipxe node now gets tftp://<bracketed server>/<UEFI loader>, and the loader name comes from BootPolicy->x86_loader, which is the one place it is chosen. No URL is written when that file is not on disk, because naming a file the TFTP server does not have costs the client a timeout it cannot diagnose; the Kea client classes already refuse it for the same reason. xnba keeps its exclusion. Its loader reports one ipv6 string against a control of five, where the iPXE loader reports five against 26, so there is no evidence it reads option 59. Captured by xCAT-test/unit/dhcp_dhcpv6_duid.t. Removing ipxe from the gate fails the first assertion; removing the on-disk check fails the second. Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>