mirror of
https://github.com/xcat2/xcat-core.git
synced 2026-11-20 17:32:15 +00:00
657ff339e1
site.nameservers holds one list for the whole cluster, and on a normal lab it names IPv4 resolvers. _static_kickstart_network6 in Template.pm kept only the entries that resolve to an IPv6 address, so it rendered no --nameserver at all and the installed node had no /etc/resolv.conf. Measured on a riscv64 openEuler install. EL 10 takes the same path, and EL 8 and EL 9 now take it too, so the number of nodes exposed grows. _autoyast_network6 in the same file already answered this: it maps '<xcatmaster>' through ipv6_server_for_node and falls back to the management node when the cluster configures no IPv6 resolver. The chooser is now one sub, _ipv6_nameservers_for_node, and both callers use it. The fallback is the management node and not the gateway, because a gateway can be a router that serves no DNS. A management node with no address on the network of the node yields no resolver, rather than a guess. template_ipv6_rendering.t asserts the rendered network line for all three cases. Without the fallback the IPv4-resolver case fails while the configured IPv6 resolver case and the no-address control keep passing, and autoyast_ipv6_network.t goes red with it, which shows both callers read the same chooser. Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>