2
0
mirror of https://github.com/xcat2/xcat-core.git synced 2026-11-22 10:22:18 +00:00
Commit Graph

29347 Commits

Author SHA1 Message Date
Daniel Hilst 3fbf0b2a85 fix(xcat-test): a conf value is cut at its first semicolon
The value class of the conf parser held ':' and '/' and not ';', so
"othersettings=cpumode:host-passthrough;firmware:efi-secureboot" was read as
"cpumode:host-passthrough" and the rest was dropped with no warning. chtab
wrote the row with the first setting alone, and the node was defined without
the firmware it needs to boot over IPv6. The [Object_*] branch had the same
class and the same effect on vmothersetting.

The chtab command was also built by interpolation, with the row selector
unquoted, so a row name or a key carrying shell syntax would have ended the
command. chdef left its type and object name unquoted for the same reason.

parse_conf_assignment is now the one place the class is written, for both
section kinds. table_row_command builds the chtab command with every argument
quoted, the row selector among them, and object_definition_command quotes its
type and name.

xcattest_object_quoting.t asserts the argument list each command delivers, not
only its text, so a quoting change that splits an argument is caught. Removing
';' from the class fails the one check that names a semicolon value and leaves
the other fifteen passing.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-30 13:17:39 -03:00
Daniel Hilst 102dc80920 fix(postscripts): an installed node ignores the DUID its reservation holds
configdhcpv6duid always derived the DHCPv6 client identifier from the SMBIOS
UUID in firmware byte order. makedhcp does that only when mac.duid is unset or
holds 'firmware': 'canonical' reserves the order product_uuid prints, and a
literal DUID is reserved as it stands. A node with either setting wrote an
identifier that matched no reservation, so it took a pool address and had no
boot file URL.

mypostscript.tmpl now exports the attribute as DHCP6DUID, and the postscript
reads it. 'canonical' keeps the order product_uuid printed. A literal is
written as it stands for NetworkManager, which takes a whole DUID.
systemd-networkd composes one from a named type, and only the UUID type can be
expressed that way, so a literal of another type is written for
NetworkManager alone and the reason is logged. A value that is neither keyword
nor DUID writes nothing, which is what makedhcp refuses as well.

The derived values are byte-identical to kea_duid_from_uuid for both orders.
postscript_dhcpv6_duid.bats goes from 9 checks to 16; ignoring the attribute
fails the five that name a setting and leaves the firmware default passing.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-30 13:17:39 -03:00
Daniel Hilst 8c704104ab fix(template): the AutoYaST profile gives a node its gateway as a resolver
_autoyast_network6 replaced '<xcatmaster>' in site.nameservers with the
gateway of the node, and fell back to the gateway when the list held no IPv6
address. '<xcatmaster>' is the management node, which runs named. The gateway
is not: a cluster whose gateway is a separate router gave every node a
resolver that answers nothing, and a cluster with no gateway gave none at all,
so the installed node resolved no hostname.

The placeholder now resolves through ipv6_server_for_node, which is what the
gateway itself already used. A value that is not an address is not written,
so an unresolvable placeholder leaves the list empty rather than putting
"<xcatmaster>" in the profile.

autoyast_ipv6_network.t gains a management node that is nobody's gateway, so
the two can be told apart, and the check that asserted the old behaviour now
asserts the new one. Restoring the gateway fails five checks and leaves the
other nineteen passing.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-30 13:17:23 -03:00
Daniel Hilst 7f46d8dab3 fix(ipv6): an NFS root loses the last group of its IPv6 server
substitute_facing_address brackets the facing address only where a port
follows the placeholder. An NFS root carries the server between two colons,
as in "root=nfs:!myipfn!:/install/netboot", so an IPv6 server came out as
"root=nfs:2001:db8::1:/install/netboot". dracut reads the server up to the
last colon, so it took "2001:db8:" and the statelite node could not mount its
root.

The substitution now also brackets a placeholder that an NFS path follows. A
placeholder with nothing after it still takes the bare address, because
xcatd=!myipfn! names a host with no port and the postscripts read that value
as it stands.

networkutils_ipv6_helpers.t covers both forms in one command line. Removing
the new substitution fails the two IPv6 checks and leaves the IPv4 and
bare-placeholder checks passing.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-30 13:17:23 -03:00
Daniel Hilst c0f8fd42b0 feat(debian): an IPv6-only node installs Ubuntu from the ISO over HTTP
An IPv6-only node could not install Ubuntu. subiquity_boot_params refused it,
because casper mounts the live filesystem with klibc nfsmount, which has no
IPv6: it answers "need a path" for "[2001:db8::1]:/export" and for
"2001:db8::1:/export", while an IPv4 server gets past parsing to the mount.
casper takes nfsroot= as an opaque path, so no option changes the family.

casper has a second route. do_urlmount downloads an ISO with casper's own
wget, which speaks IPv6, and loop-mounts it, and the network itself was never
the limit: init parses ip6= and configure_networking runs "dhcpcd -1KL -6" on
it. The route needs an ISO to fetch, and xCAT serves the extracted media and
kept no ISO.

copycds now passes the ISO it was given to the distribution plugin, which
links it into the install tree as install.iso. A symbolic link, because the
Ubuntu 24.04 ISO is 3.2G, and the xcat.conf xCAT ships gives /install
"Options FollowSymLinks". A block device has no path to link and passes none.

An IPv6-only node then gets "ip6=dhcp boot=casper netboot=url
url=http://[server]:port/install/<os>/<arch>/install.iso", with no nfsroot
and no toram: do_urlmount already holds the ISO in the initramfs tmpfs, so
copying the live filesystem again only doubles the memory the node needs.
That memory is the cost of the route -- 3.2G for the ISO on top of the
installer -- so a node with 4G cannot take it.

An IPv4 node is untouched and still mounts its root over NFS. A tree copied
before this change carries no ISO, so such a node is refused as before, with
a message naming install.iso and copycds.

debian_subiquity_boot_params.t goes from 17 checks to 36. Routing an IPv6-only
node back to the NFS form fails the six HTTP checks; dropping the bracketing
fails exactly the two bracketing checks; and returning success from
link_install_iso without creating the link fails the three that read the link
back, while the one that reads the return value still passes.

Not yet booted on a cluster.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-30 10:42:54 -03:00
Daniel Hilst 8cfb0c60a9 fix(debian): the Subiquity refusal names the wrong component
subiquity_boot_params refuses an IPv6-only node and says the live installer
"configures its network and mounts its root with klibc, which has no IPv6
support". The first half is wrong. casper reads ip6= from the kernel command
line and configures the interface with dhcpcd -6, which speaks DHCPv6:
scripts/functions runs "dhcpcd -1KL -t $ROUNDTTT -6" on the ip6= value, and
init parses ip6= at line 156. klibc ipconfig is only the IPv4 branch.

The one component with no IPv6 is klibc nfsmount, which casper uses for the
live filesystem. Measured on noble klibc-utils 2.0.13: it answers "need a
path" for "[2001:db8::1]:/export" and for "2001:db8::1:/export", while an
IPv4 server gets past parsing to the mount, and the binary carries no inet6
string against seven nfs and mount strings.

The refusal stands, because casper takes nfsroot= as an opaque path and has
no way to pass it an address family. Only its reason changes. The comment
also records the route that would close this: netboot=url fetches an ISO with
casper's own wget, which does IPv6, and that is a different provisioning
method than the extracted tree xCAT exports.

The check on the message matched /klibc/, which is the family and not the
component, so it passed for any klibc tool. It now matches /nfsmount/, and
the previous wording fails it.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-30 10:31:41 -03:00
Daniel Hilst ec5acc96a1 fix(yaboot): a dual-stack node is linked to a boot configuration name no firmware asks for
yaboot links its configuration file to one name for each address of the node
in the mac table. The name is sprintf("%02x%02x%02x%02x", split(/\./, $ip)),
and an IPv6 address has no four octets: sprintf reads the first field as a
number and fills the rest with zeroes, so 2001:db8:156::10 gives 7d1000000.
A dual-stack node therefore got one correct link and one link to a name no
firmware requests, with no warning. An IPv6-only node got only the second.

yaboot_config_name returns a name only for an address with four octets in
range, and the loop passes over anything else. A node that produced no name
at all is reported with what to use instead, rather than reporting success.

The facing address was found with my_ip_facing, which resolves with inet_aton
and reports an IPv6-only node unresolvable. yaboot_facing_address asks
node_address_family first, the way grub2.pm and petitboot.pm do, and the
!myipfn! substitution goes through substitute_facing_address so a placeholder
that a port follows is bracketed.

The error for a node with no facing address and no service node interpolated
$myname, which is declared in the branch above it and not in that one. The
file has no "use strict", so the message read ": " and the name of the
management node was lost. It now determines the name where it uses it.

yaboot_ipv6.t covers both subs. Restoring the unguarded sprintf fails the
four name checks; calling my_ip_facing unconditionally fails the three family
checks. The IPv4 checks pass under both, which is what tells the two defects
apart from a test that dies.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-30 10:23:38 -03:00
Daniel Hilst 6dcde28dc9 fix(petitboot): an IPv6-only node is given a boot configuration name no firmware asks for
petitboot asks for a configuration file named after the four octets of the
IPv4 address of the node, in hexadecimal. The name is built with
sprintf("%02x%02x%02x%02x", split(/\./, $ip)), and an IPv6 address has no
four octets: sprintf reads the first field as a number and fills the rest
with zeroes, so 2001:db8:156::10 gives 7D1000000. nodeset then links the
configuration to a name no firmware requests, reports success, and the node
boots nothing.

petitboot_config_name returns the name only for an address that has four
octets in range, and nodeset reports the node instead of linking a name that
cannot work. The message says what to use: an IPv4 address on the node, or
netboot=grub2, which carries the server in the boot file URL and needs no
name of this form.

This is a refusal, not support. What name petitboot asks for over DHCPv6 is
not established here, and no cell in the lab runs petitboot, so the value
cannot be measured. An error that names the limit is what an operator can
act on; a wrong name is not.

Five checks in petitboot_ipv6.t cover it. Restoring the unguarded sprintf
fails the three IPv6 and undef checks and leaves the two IPv4 checks passing,
including the name of 192.0.2.50, which stays C0000232.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-30 10:15:49 -03:00
Daniel Hilst 9cc9503a96 fix(petitboot): an IPv6 node loses the server from its kernel and initrd URL
petitboot builds the URL it fetches a kernel and an initrd from as
"$httpmethod://$installsrv:$httpport$tftpdir/", so an IPv6 install server
gives "http://2001:db8::1:80/tftpboot/...", which cannot be split into a host
and a port. The node then has no server to fetch from.

The facing address is found with my_ip_facing, which resolves with inet_aton.
An IPv6-only node is reported unresolvable, and the node gets no
configuration at all.

petitboot_boot_url builds the URL through uri_authority, which brackets an
IPv6 address. petitboot_facing_address asks the family of the node which
helper answers, the way grub2.pm does. The three !myipfn! substitutions go
through substitute_facing_address, which brackets the placeholder that a port
follows and leaves every other one bare. petitboot.pm also now loads
xCAT::NetworkUtils, which it has always used and never named.

An IPv4 node keeps the URL it had, byte for byte, including the port that the
old form always wrote.

petitboot_ipv6.t covers both. Writing "$server:$port" back in place of
uri_authority fails the two IPv6 URL checks. Calling my_ip_facing
unconditionally fails the three family checks. Neither mutation touches the
IPv4 checks, which is what separates the two defects from a test that dies.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-30 10:15:36 -03:00
Daniel Hilst 38a60074e0 fix(dhcp): a unit test writes the radvd configuration of the host it runs on
configure_router_advertisements writes /etc/radvd.conf and runs sysctl on the
management interface. dhcp_dhcpv6_duid.t drives makedhcp through
process_request, so the test reaches both. The suite runs as root in the
GitHub CI, where the test therefore replaces the real /etc/radvd.conf of the
runner and turns IPv6 forwarding on for its interfaces.

Where the file is not writable the warning also reaches the callback that
other checks read, so the test failed on an unprivileged host:

  Structures begin differing at:
       $got->[2] = 'Cannot write /etc/radvd.conf, so the IPv6 networks
                    announce no route: Permission denied'
  $expected->[2] = Does not exist

The path is now the package variable $radvdconffile, and the sysctl call is
the sub enable_ipv6_forwarding. The test localizes both, the way it already
localizes $dhcpconffile and xCAT::Utils::restartservice.

Six checks now cover the behaviour the configuration carries: the file is
written, it names the interface of the IPv6 network, the interface sends
advertisements, the managed flag is on, the prefix is announced, and
forwarding is enabled. Removing the call from the ISC path fails exactly
those six and leaves the other 127 passing.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-30 10:15:08 -03:00
Daniel Hilst 0312d28117 fix(dhcp): makedhcp -n writes no router advertisement
kea_process_request has two paths. The full regeneration writes the whole
configuration, restarts the services, unlocks and returns; the incremental one
falls through to the end. The call added in the previous commit sat only on the
incremental path, so makedhcp -n, which is what configures a new cluster, wrote
no /etc/radvd.conf at all.

Measured on an IPv6-only alma10.1 management node: with radvd.conf removed,
radvd stopped and forwarding set to 0, makedhcp -n left all three unchanged.
The generator itself was correct the whole time; it was never called.

The full regeneration now configures the advertisements before it returns.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-29 18:14:38 -03:00
Daniel Hilst 113463a191 feat(dhcp): an IPv6 network announces no prefix and no route
makedhcp writes the DHCPv6 reservations and nothing announces the network. xCAT
configures no router advertisement anywhere: a fresh IPv6 provision network has
no radvd and forwarding off.

Two failures follow from that one gap. A client that follows RFC 4861 uses
DHCPv6 only when an advertisement sets the managed flag, so iPXE reported
"No configuration methods succeeded" and never sent a solicit: the DHCPv6 log
held the firmware DUID alone. And a client that does solicit gets one address
with a prefix length of 128, because the on-link prefix and the default route
come from the advertisement, not from DHCPv6.

makedhcp now writes /etc/radvd.conf for every IPv6 network in the networks
table and restarts radvd, for both the ISC and the Kea backend. The
advertisement sets the managed flag and marks the prefix on-link but not
autonomous, so the address still comes from DHCPv6, which holds the
reservations. An IPv4 cluster gets no file and no service. A management node
without radvd gets a warning naming what the nodes lose.

Measured on an IPv6-only alma10.1 node with netboot=ipxe. Without the
advertisement iPXE stopped at "No configuration methods succeeded". With it
iPXE reported "Configuring (net0 ...) ok" and
"net0: 2001:db8:149::1002/64 gw fe80::4054:ff:fec9:95d3", loaded the kernel,
and the node booted and answered ssh, xdsh and updatenode over IPv6.

Captured by xCAT-test/unit/radvd_config.t. Removing the managed flag fails the
assertion that names it; making the prefix autonomous fails the assertion that
names that.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-29 17:55:55 -03:00
Daniel Hilst c2c5bc8bb6 docs(dhcp): the iPXE loader cannot finish an IPv6 boot yet
The commit that added ipxe to the DHCPv6 gate justified it with strings found
in snponly.efi. That was not evidence that the feature is built in, and a boot
disproved it.

Measured on an IPv6-only alma10.1 node with ipxe-xcat 2.0.0: the firmware does
fetch the shim over IPv6 from the option this code sends, the shim chains to
snponly.efi, and iPXE then reports "No configuration methods succeeded" on a
network whose only DHCP server is DHCPv6. iPXE never reaches the script.

The option stays, because it is what xCAT owes a client that asks, and the node
fails at the same point without it. The comment now records what the loader
cannot do, so the next reader does not repeat the strings test.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-29 17:44:32 -03:00
Daniel Hilst adeb938962 fix(xnba): the kernel and initrd URLs of an IPv6 node lose their server
The previous commit replaced !myipfn! with the facing address, which fixed the
kernel command line. It left the eleven other places where setstate writes
${next-server} into the script directly, among them the imgfetch lines for the
kernel and the initial ramdisk. An IPv6 node resolved those to
"http:///tftpboot/..." and had no server to fetch its kernel from.

Measured on an IPv6-only alma10.1 node: the script carried
"http://[2001:db8:149::1]:80/install/..." for the command line and
"http://${next-server}/tftpboot/.../vmlinuz" for the kernel.

The server is now computed once in setstate and used at every site, so the
whole script names one server. An IPv4 node still gets ${next-server}, which
iPXE fills from its own offer.

netboot_ipxe_method.t and secureboot_ipxe_node_shim.t load xnba.pm against a
stub of xCAT::NetworkUtils. The stub gains the two methods setstate now calls,
and both tests describe their nodes as IPv4, which keeps ${next-server}.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-29 17:26:26 -03:00
Daniel Hilst 7514b931b3 fix(xnba): an IPv6 node loses the server from every URL in its iPXE script
xnba.pm writes ${next-server} in place of !myipfn! and lets iPXE fill it from
the DHCP offer. next-server is a DHCPv4 field, so an IPv6 node resolves it to
the empty string and every URL in the script loses its host. The fallback does
not help either: my_ip_facing resolves with inet_aton, so it reports an
IPv6-only node unresolvable.

The script now carries the facing address of the management node when the node
has an IPv6 address, bracketed because the script puts it in a URL. The lookup
names the family, the way grub2.pm does. An IPv4 node keeps ${next-server}, so
nothing changes for it.

ipxe.pm runs this code with SCRIPTS and METHOD set to its own, so the change
reaches netboot=ipxe as well as netboot=xnba.

xnba.pm also calls xCAT::NetworkUtils eight times without loading it, and works
only because another module does. The use is now explicit.

Captured by xCAT-test/unit/ipxe_script_server.t. Ignoring the family fails five
of its seven assertions and leaves the two IPv4 ones passing.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-29 16:59:24 -03:00
Daniel Hilst 25720c77a7 feat(dhcp): an ipxe node gets no boot file over DHCPv6
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>
2026-10-29 16:55:47 -03:00
Daniel Hilst cd67199463 fix(netboot): an IPv6-only diskless node boots with no address
xcatroot writes the netplan of the booted system from the interface it found,
and it always wrote "dhcp4: true". An IPv6-only node has no DHCPv4 server, so it
reached its login prompt with no address: Ubuntu 24.04.5 reported
"[FAILED] Failed to start systemd-networkd-w... Wait for Network to be
Configured." and "[FAILED] Failed to start xcatpostinit.service", and the node
answered no ssh.

The address is already on the kernel command line, in the static form dracut
takes. xcat_static_ip6_fields reads it and the netplan carries the address, the
prefix and a default route through the gateway. A node whose command line holds
an IPv4 form keeps dhcp4, because the fields are read only from a bracketed
literal.

Captured by xCAT-test/bats/ipv6_xcatroot_netplan.bats. Reading the fields by
cutting on the first colon, which is what an IPv6 literal breaks, fails the
three parsing assertions and leaves the four refusals passing.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-29 16:01:34 -03:00
Daniel Hilst 77eaf4d53c fix(ipv6): a diskless node has an address and no route
mknetboot gave an IPv6-only node ip=either6, which asks dracut for DHCPv6.
DHCPv6 assigns one address with a prefix length of 128 and carries no route, and
an xCAT provision network sends no router advertisement: radvd is not installed
and net.ipv6.conf.<nic>.forwarding is 0. The node came up with the address and
no way to reach the server, and the dracut hook reported
"Connecting to [2001:db8:147::1]:80... failed: Network is unreachable."

debian.pm now builds the static form from the address, gateway and prefix the
node already has in the database, the way sles.pm passes hostip and gateway to
linuxrc. either6 remains the answer when the address cannot be resolved.

Captured by xCAT-test/unit/dracut_static_ip6.t. Removing the prefix length from
the parameter fails four of its nine assertions and leaves the bracketing and
the refusal cases passing.

Measured on an IPv6-only Ubuntu 24.04 node: Kea records prefix_len=128 for its
lease, and dracut logged BOUND6 for eth0 before the fetch failed.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-29 15:27:53 -03:00
Daniel Hilst ddaad73ab4 fix(grub2): a ppc node is given linuxefi when its image carries it
grub2_kernel_commands read the image and not the architecture, so a ppc node
whose grub2 image carries linuxefi was given it. linuxefi loads an EFI binary
and a ppc loader is not one. The previous commit removed the architecture test
along with the defect it carried.

The command now needs both: the architecture whose loader is an EFI binary, and
an image that carries the command.

grub2_netboot_protocol.t covers the three architectures and caught this. Its
loader fixture now records the commands it carries, because the configuration
follows the image.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-29 15:27:53 -03:00
Daniel Hilst 075e6801e9 fix(grub2): an x86 node stops at the menu with "can't find command `linuxefi'"
setstate in grub2.pm appends "efi" to the kernel and initrd commands for every
node whose architecture matches x86, so the configuration reads linuxefi and
initrdefi. Both come from a downstream patch. grub2-xcat 2.12-2 for Ubuntu is
built from upstream grub and carries neither, so the node loads the loader and
its own configuration over TFTP, prints "can't find command `linuxefi'", asks
for no kernel, and waits at the menu until it is powered off.

The pair now comes from the image served to the node. BootUtils reads the
image, which records the name of every command its modules register, and
answers linuxefi and initrdefi only when the image carries them. An image that
cannot be read is answered with linux and initrd, which every grub2 image
carries.

This reaches a node only when it netboots with grub2. An IPv6 node has no other
loader, because bootfile-url is written for grub2 alone.

Measured on an IPv6-only Ubuntu 24.04 node: with linuxefi the node made no TFTP
request for the kernel; with linux it loaded the kernel and the initial ramdisk
and printed no error.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-29 14:45:34 -03:00
Daniel Hilst 557c3689f7 test(grub2): a grub2 image without linuxefi is still offered linuxefi
grub2.pm chooses the kernel command from the architecture of the node, so every
x86 node is given linuxefi and initrdefi. Those two come from a downstream patch
and an image built from upstream grub carries neither.

These assertions fail without the fix that follows: the upstream image, the
missing image and the undefined image are all answered with linuxefi.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-29 14:45:33 -03:00
Daniel Hilst 2f6f029382 fix(xcat-core): a diskless node has no server in its imgurl
mknetboot in debian.pm builds the imgurl from the image server, which is the
'!myipfn!' placeholder whenever noderes.tftpserver and noderes.xcatmaster are
unset. Commit 7ab362835 wrapped that value in format_host_port so an IPv6
server would be bracketed. format_host_port refuses the placeholder, because
format_uri_host validates it as a host name, so the imgurl lost its server and
its port and read "imgurl=http:////install/netboot/.../rootimg.cpio.gz". The
node then had no address to fetch its root image from. This reached every
Ubuntu diskless node, not only an IPv6 one: upstream interpolated the value
directly and the placeholder survived to be substituted.

format_uri_host now returns the placeholder unchanged, the way uri_authority
already passes it through for the XCAT= parameter. The boot loader plugins
substitute it afterwards, and substitute_facing_address brackets it when the
facing address is IPv6.

Measured on an IPv6-only Ubuntu 24.04 node: the grub2 command line now carries
imgurl=http://[2001:db8:147::1]:80/install/... beside ip=either6.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-29 13:49:07 -03:00
Daniel Hilst 5760b73d57 test(networkutils): the facing-address placeholder is dropped by format_host_port
format_host_port validates its host with format_uri_host, which refuses
'!myipfn!' because it is not a host name. The call returns undef, so a command
line built from it loses both the server and the port.

These assertions fail without the fix that follows: format_host_port and
format_uri_host return nothing for the placeholder, and the imgurl built from it
reads "imgurl=http:///install/..." for an IPv6 and an IPv4 facing address alike.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-29 13:49:07 -03:00
Daniel Hilst 1c8094e305 fix(template): the IPv6 search list makes YaST refuse the whole profile
The search list added in the previous commit carried no config:type, and the
AutoYaST schema gives searchlist the LIST type, the way it gives it to
nameservers. xmllint against profile.rng of Leap 15.6 reports only "Element
profile failed to validate content", and YaST refuses the profile entirely, so
the node cannot install at all.

searchlist is now emitted as a typed list. Measured against
/usr/share/YaST2/schema/autoyast/rng/profile.rng on a live management node: the
generated profile fails to validate, the same profile with the attribute added
validates, and removing hostname as well changes nothing, so hostname was not
the element at fault.

Captured by xCAT-test/unit/autoyast_ipv6_network.t, which gained an assertion on
the attribute.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-29 12:48:21 -03:00
Daniel Hilst 278b582cf5 fix(template): an IPv6-only SUSE node is installed as "localhost"
_autoyast_network6 sets dhcp_hostname to false, because an IPv6-only node has no
DHCPv4 to take a hostname from, and it writes no hostname of its own. YaST then
has nothing to set: y2log of an installed node records Y2Network::Hostname with
@static=nil, @transient=nil and @dhcp_hostname=:none, and the node answers
"localhost". The two sibling builders in the same file write both keys.

The dns section now carries the node name and a search list of the node domain.
getNodeNetworkCfg6 already returns the name, so no new lookup is needed.

Captured by xCAT-test/unit/autoyast_ipv6_network.t. Without the two keys its
assertions 17 and 18 fail and the other 16 pass.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-29 12:26:20 -03:00
Daniel Hilst 0ac354f931 fix(sle): an IPv6 install server empties the AutoYaST profile
pre.sle substitutes the install server for XCATNEXTSERVERHOOK in the media_url
that xCAT::Template writes for every install source. The substitution read
sed -e 's!XCATNEXTSERVERHOOK!'$nextserver'!', with the value unquoted, and
shopt -s nullglob is set earlier in the same script. An IPv6 server is bracketed,
so "[2001:db8::1]" is a glob that matches no file and the whole sed script word
is removed. sed then reads the profile as its script and writes nothing, so
/tmp/profile/modified.xml is empty. AutoYaST falls back to the unmodified profile
and stops on "Disk 'XCATPARTITIONHOOK' was not found", because the pre-script
also substitutes the install disk into that profile.

The substitution moves into substitute_nextserver, which quotes the value. An
IPv4 server was never affected, because it carries no bracket.

Captured by xCAT-test/bats/ipv6_pre_sle_nextserver.bats. With the quotes removed
again, assertions 9 and 10 fail and the IPv4 assertion 11 still passes.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-29 11:53:52 -03:00
Daniel Hilst f094586706 fix(template): the AutoYaST profile gives an IPv6-only node an IPv4 resolver
_autoyast_network6 passed the node nameserver list through unchanged, so an IPv6-only
node was configured with the IPv4 resolver that site.nameservers names for the cluster.
The node cannot reach it, and an unreachable server in resolv.conf costs every lookup
a timeout.

The list now keeps only the IPv6 servers. When that leaves none, the gateway stands
in, which is the management node and already answers for the node. The <xcatmaster>
substitution is unchanged.

Captured by xCAT-test/unit/autoyast_ipv6_network.t, where two of its sixteen
assertions fail without this change.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-29 09:58:17 -03:00
Daniel Hilst 7fd7ee7d92 test(template): an IPv6-only node is given an IPv4 resolver it cannot reach
site.nameservers holds one list for the whole cluster, so an IPv6-only node takes the
IPv4 resolver of an IPv4 network when its own network names none. The AutoYaST profile
of a Leap 15.6 node carried <nameserver>192.168.156.1</nameserver> while the node had
no IPv4 address at all.

An unreachable server in resolv.conf is not a failure the node reports. Every lookup
waits for its timeout before the next server is tried.

The test adds a node whose configured resolvers are IPv4 only and asserts the section
carries none of them, and that the gateway stands in.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-29 09:58:17 -03:00
Daniel Hilst 8eb12a1392 fix(template): an IPv6-only node has its static address rewritten to DHCP
An IPv6-only openSUSE node completed its install with the static IPv6 address in its
AutoYaST profile, then booted with a link-local address only. The applied profile on
the node carried bootproto static and the address, and ifcfg-eth0 read BOOTPROTO=dhcp
with a modification time later than the install.

post.sles.common writes that file. It keeps the interface configuration only when
MANAGEDADDRESSMODE reads static, and managed_address_mode returned
site.managedaddressmode, which was unset. xCAT wrote the static configuration and then
removed it.

managed_address_mode now takes the node and reports static for a node that
xCAT::NetworkUtils::node_is_ipv6_only reports as IPv6-only. A node with any IPv4
address keeps the site value, so an IPv4 and a dual-stack cluster are unchanged.

Captured by xCAT-test/unit/template_ipv6_rendering.t, where one of the three new
assertions fails without this change.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-29 09:56:37 -03:00
Daniel Hilst 2a6d80fb8c test(template): the address mode is answered for the cluster, not for the node
post.sles.common reads MANAGEDADDRESSMODE and, for anything but static, removes the
interface configuration and writes a new one with BOOTPROTO=dhcp. managed_address_mode
returns site.managedaddressmode, which describes the cluster.

An IPv6-only node therefore has the static IPv6 configuration in its AutoYaST profile
rewritten to DHCP during the post phase, and comes up with a link-local address only.
The node has no IPv4 address to ask a DHCP server for, so the site attribute cannot
answer for it.

The test renders MANAGEDADDRESSMODE for three nodes with the site attribute set to
dhcp: an IPv6-only node, an IPv4 node and a dual-stack node. Only the IPv6-only node
is expected to differ, so the other two hold the site behaviour down.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-29 09:56:37 -03:00
Daniel Hilst 582fd157f2 fix(ipv6): an IPv6-only Ubuntu diskless node gets a DHCPv4 initrd
The Ubuntu diskless kernel command line carries no dracut ip= parameter. dracut then
configures the interface it needs with DHCPv4, so an IPv6-only node comes up with no
global address, cannot fetch imgurl and never mounts a root.

gen_net_boot_params now returns ip6 beside the ip it already derived, spelled either6,
which asks dracut for DHCPv6 and falls back to router advertisement. debian.pm appends
it for a node that xCAT::NetworkUtils::node_is_ipv6_only reports as IPv6-only, so an
IPv4 node is told exactly what it was told before. The ip the EL path reads is
unchanged.

Captured by xCAT-test/unit/networkutils_dracut_ipv6_boot_param.t. This closes the
derivation; the Ubuntu diskless path is not yet proven end to end on a cluster.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-29 09:09:23 -03:00
Daniel Hilst 918ed688de test(ipv6): nothing gives the dracut initrd an IPv6 network parameter
An Ubuntu diskless node brings its interface up from the dracut ip= parameter.
debian.pm appends ifname, netdev and BOOTIF and no ip= at all, and dracut configures
the interface it needs with DHCPv4 when the command line carries none. An IPv6-only
node therefore gets no address, cannot fetch imgurl and never mounts a root.

gen_net_boot_params already derives the interface in xCAT's own order and returns the
IPv4 spelling of the parameter. The test asserts the IPv6 spelling beside it for every
branch that names an interface, and asserts the IPv4 spelling is unchanged, because
anaconda.pm is its only caller today.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-29 09:09:23 -03:00
Daniel Hilst d73343b198 fix(packaging): the openSUSE IPv6 module gap needs a requires, not a hard dependency
The previous commit required Socket6 and IO::Socket::INET6 on every RPM family. That
is wrong for EL and openEuler, where dnf installs a recommended package and the
existing Recommends already delivers both modules.

The gap is openSUSE only, and it has two parts. xCAT-server recommends both modules
inside a guard that names fedora, rhel and openEuler and omits suse_version, so an
openSUSE build declares neither a requires nor a recommends. perl-xCAT declares nothing
at all, although xCAT::SLP, xCAT::Client and xCAT::NetworkUtils all reach IPv6 through
these modules. A recommendation would not close it either: the openSUSE Minimal-VM
image sets solver.onlyRequires = true, so zypper installs no recommended package, which
is why xCAT already names a DHCP server directly.

Both specs now require both modules on openSUSE and recommend them on the families
whose package manager honours a weak dependency. The xCAT-server deb returns to a
Recommends.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-29 09:05:15 -03:00
Daniel Hilst edea395c29 test(packaging): the IPv6 module dependency is asserted for the wrong families
The assertions added with this test required Socket6 and IO::Socket::INET6 on every
RPM family, which contradicts xcat_server_inet6_optional_dependency.t and the reason
it records: every call site loads the modules with an eval and keeps working on IPv4,
so a hard dependency states a dependency the code does not have.

The measurement that prompted the test still holds, and it is narrower than it looked.
Both modules are absent on a Leap 15.6 management node because the openSUSE Minimal-VM
image sets solver.onlyRequires = true in /etc/zypp/zypp.conf, so zypper installs no
recommended package. dnf installs one, so EL and openEuler need no hard dependency.

The test now reads requires and recommends separately per family: openSUSE requires
both and recommends neither, EL and openEuler recommend both and require neither. The
deb control files are read per package, since perl-xCAT has carried a hard dependency
since before this rule. xcat_server_inet6_optional_dependency.t gains a pointer to the
openSUSE exception so the two files do not disagree in prose.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-29 09:05:15 -03:00
Daniel Hilst 174668fb60 fix(sles): an IPv6 install server reaches the media_url as "[2001"
The nextserver derivation in pre.sle and pre.sles split the URL authority at the
first colon, which splits an IPv6 literal. YaST then had no usable install source
on a SLE15 or SLES12 node installed over IPv6.

Both scripts now read the authority with the bracket-aware form pre.rhels10 already
uses, and put the brackets back when the host is an IPv6 address, because the value
goes into a media_url. A portless IPv4 URL no longer keeps its path.

Captured by xCAT-test/bats/ipv6_pre_sle_nextserver.bats, which fails 5 of its 8
assertions without this change.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-29 08:56:37 -03:00
Daniel Hilst c86de4f7a9 test(sles): the SUSE installer cuts an IPv6 install server at its first colon
pre.sle and pre.sles read the install server out of the kernel command line and put
it back into a URL. pre.sle substitutes it for XCATNEXTSERVERHOOK in the media_url of
every install source, and pre.sles substitutes it into #INSTALL_SOURCES_IN_PRE#.

The derivation cut the authority at the first colon. An IPv6 install server written
"autoyast=http://[2001:db8::1]:80/install/autoinst/node01" yielded "[2001", so the
media_url read "http://[2001:80/install/..." and YaST had no install source. A
portless IPv4 URL kept its path as well, and worked only because xCAT always writes
a port.

The test runs the derivation taken from each script against a command line of its
own, so a change to the derivation is measured here.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-29 08:56:37 -03:00
Daniel Hilst bf3a2f066b fix(packaging): SLP discovery and IPMI over IPv6 are off on an openSUSE node
Socket6 and IO::Socket::INET6 are absent on a Leap 15.6 management node that carries
every other xCAT dependency, so $ip6support in xCAT::SLP and $doipv6 in xCAT::IPMI
evaluate to 0. SLP discovery and IPMI over IPv6 then do nothing and report no error.

Both packages exist: perl-Socket6 and perl-IO-Socket-INET6 are in the openSUSE main
repository and in the EL appstream repository. Nothing asked for them. perl-generators
reads a use statement, and every caller uses eval { require ... }, so the EL build
derives no perl(Socket6) either. xCAT-server named the deb packages as Recommends,
which apt 3.0 solver3 drops when it cannot place them.

perl-xCAT and xCAT-server now require both modules on every RPM family, and the
xCAT-server deb moves them from Recommends to Depends.

Captured by xCAT-test/unit/ipv6_socket_modules_declared.t, which fails 16 of its 20
assertions without this change.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-29 08:52:27 -03:00
Daniel Hilst 7703372cc2 test(packaging): nothing declares the two Perl modules every IPv6 path needs
xCAT::SLP, xCAT::IPMI, xCAT::Client, xCAT::NetworkUtils and the dhcp, nodestat and
credentials plugins reach IPv6 only through Socket6 and IO::Socket::INET6. Each one
loads them with eval { require ... }, so a missing module is not an error. The guard
variable stays false and the IPv6 branch is never taken.

No family declares the dependency. perl-generators reads a use statement, not a
require inside an eval, so the EL build derives no perl(Socket6) either, and
xCAT-server lists the two deb packages as Recommends, which apt 3.0 solver3 can drop.

The test asserts both specs require both modules on openSUSE, EL and openEuler, and
that both deb control files name them in Depends.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-29 08:52:19 -03:00
Daniel Hilst 2bb169e04f fix(template): an IPv6 node installs and then boots with no address
_autoyast_network6 builds a networking section with a static interface, but did
not set keep_install_network. AutoYaST then keeps the network the installer
used and ignores the interface in the profile.

The node installed over IPv6 and booted with ifcfg-eth0 BOOTPROTO=dhcp and no
address but a link-local one. xcat.sh could not reach the management node:
"logger: failed to connect to 2001:db8:156::1 port syslog-conn" and
"connect: Network is unreachable", so no postscript ran and the node never
registered.

The section now sets keep_install_network to false, which is what makes AutoYaST
write the static interface.

Measured on the installed node: /etc/sysconfig/network/ifcfg-eth0 carried
BOOTPROTO=dhcp and the only address was fe80::4078:c0ff:fea8:9c0a.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-28 14:48:37 -03:00
Daniel Hilst d1cafdddc3 test(template): the IPv6 profile does not replace the installer network
AutoYaST keeps the network the installer used unless keep_install_network says
otherwise, and the sections _autoyast_network6 replaces set it true. The static
interface in the generated section was therefore ignored.

The test asserts the section sets keep_install_network to false.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-28 14:48:37 -03:00
Daniel Hilst 29413b5b0e fix(template): an IPv6 node gets an AutoYaST profile that YaST refuses
_autoyast_network6 emitted dhcp_resolv in the dns block of the networking
section. The AutoYaST schema of Leap 15.6 does not accept that element, and one
element it refuses invalidates the whole profile: YaST reported "Extra element
networking in interleave", then "A profile for this machine could not be found
or retrieved", and the installation stopped.

dhcp_resolv says whether DHCP may overwrite resolv.conf. The section configures
the node statically, so there is no DHCP to keep away from resolv.conf.

Measured with the schema the installer ships, /usr/share/YaST2/schema/autoyast/
rng/profile.rng: the profile failed to validate at the networking element, and
removing dhcp_resolv alone made it validate.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-28 13:28:53 -03:00
Daniel Hilst ebefdec9f8 test(template): the IPv6 networking section carries an element the schema refuses
AutoYaST validated the generated profile and reported "Extra element networking
in interleave", then told the operator no profile could be retrieved. The
element is dhcp_resolv, which the schema of Leap 15.6 does not accept.

The test asserts the section has no dhcp_resolv and keeps dhcp_hostname, which
the schema does accept.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-28 13:28:53 -03:00
Daniel Hilst 9f5d9be84f fix(sles): the installer of an IPv6-only node configures IPv4 and reaches nothing
sles.pm gave linuxrc no network arguments beyond the net device. linuxrc
configures IPv4 by default, so an IPv6-only node sent an IPv4 DHCPDISCOVER,
received "no/incomplete answer", and reported "Failed to download AutoYaST
file" without ever contacting the install source.

static_ipv6_boot_args() adds ipv6only=1 with the address, prefix, gateway and
IPv6 nameserver of the node. The node is configured statically for the reason
anaconda.pm configures EL statically: the firmware answers DHCPv6 with the
RFC 6355 DUID-UUID that the reservation is keyed on, while the installer builds
a DUID of its own that matches no reservation.

Measured on a Leap 15.6 node: with these arguments the installer fetched
control.xml from http://[2001:db8:156::1]:80/install/leap15.6/x86_64/1 from its
own address 2001:db8:156::10. Without ipv6only=1 linuxrc ignores the rest and
stays on IPv4.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-28 13:24:43 -03:00
Daniel Hilst b3cb867b87 test(sles): an IPv6-only node gets no installer network configuration
sles.pm put only the net device on the command line, so linuxrc configured IPv4
by default. An IPv6-only node sent an IPv4 DHCPDISCOVER, which the management
node answered "no free leases".

The test covers the arguments for a node with a gateway and an IPv6 nameserver,
for one with neither, that an IPv4 nameserver is left out, and that a node with
no IPv6 configuration gets no arguments.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-28 13:24:43 -03:00
Daniel Hilst 60d0176d14 fix(dhcp): no range6 is written for an IPv6 subnet that has a dynamic range
addnet6 read the dynamic range from $netcfgs{$net}, where $net is the subnet it
writes, "2001:db8:156::/64". addrangedetection stores the range under
networks.net, "2001:db8:156::", so the lookup always missed and makedhcp warned
"No dynamic range specified" for a network whose row declares one.

The subnet then carried no range6, and a DHCPv6 client whose DUID matches no
reservation received no address. The SUSE installer is such a client: linuxrc
builds its own DUID rather than the DUID-UUID the firmware sends, so it could
not get an address even though the node has a reservation for the same MAC.

dynamic_range_for() looks the range up under the subnet as written and then
under the network address alone.

xCAT-test/unit/dhcp_dhcpv6_conf_file.t fails its prefix-form assertion when the
second lookup is removed.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-28 12:40:44 -03:00
Daniel Hilst 19779fa2f8 test(dhcp): an IPv6 subnet never gets its dynamic range
addrangedetection keys the dynamic ranges on networks.net, which carries no
prefix length. addnet6 names a subnet "<net>/<prefix>" and looked the range up
under that, so the lookup missed every IPv6 subnet.

The test drives the lookup with both forms of the subnet and holds down that an
IPv4 subnet is unchanged.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-28 12:40:44 -03:00
Daniel Hilst 837509f8cd fix(xcattest): a semicolon in a conf value truncates the chdef it builds
setup_env_by_configure_file built "chdef -t $type -o $name $attr=$value" and
runcmd passes that to bash. A value containing shell syntax was read as syntax.

vmothersetting separates its settings with a semicolon, so
"vmothersetting=cpumode:host-passthrough;firmware:efi-insecure" ended the chdef
at the semicolon. The node kept cpumode alone, mkvm defined the compute node
with no firmware, and it came up as a BIOS guest. A BIOS guest cannot network
boot over IPv6 and cannot load an EFI grub2, so the node took its DHCPv6 address
and never fetched a loader.

object_definition_command() and shell_quote() build the command with every value
quoted, and the chtab path for [Table_*] quotes its values the same way.

xCAT-test/unit/xcattest_object_quoting.t fails when the quoting is removed.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-28 12:13:02 -03:00
Daniel Hilst de6c13471f test(xcattest): a conf value that carries shell syntax is not quoted
xcattest applies the [Object_*] sections of a conf by joining each attribute to
a chdef command and running it through bash. Nothing quoted the values, and a
conf carries values a shell reads as syntax.

The test builds the command for a vmothersetting that holds two settings and
asserts the semicolon stays inside one command, that every value is quoted, and
that bash passes the whole value through as one argument.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-28 12:13:02 -03:00
Daniel Hilst 84f18d5fd5 test(dhcp): nothing asserts the two backends agree on the boot file URL
dhcp6_bootfile_url_for_node builds the RFC 5970 option 59 URL for both DHCP
backends, and each backend already had its own assertions on it. Neither
compared them, so the two could drift apart and both files would stay green.

The new block renders the same node through kea_build_node_reservations6 and
through the ISC omshell session and asserts the URL is the same string, that Kea
marks it always-send, and that a node asking for xnba gets none from either
backend.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-28 12:05:35 -03:00
Daniel Hilst a27f534d43 fix(packaging): an openSUSE node cannot fetch its loader over IPv6
xCAT.spec asked for the file /usr/sbin/in.tftpd. openSUSE has two providers and
the solver installed atftp, whose server has no IPv6 option: it binds
0.0.0.0:69 only, and --bind-address :: does not change that. A node that boots
over DHCPv6 therefore received its address and its RFC 5970 bootfile-url, asked
the server for the loader, timed out, released the address and started again.

xCAT.spec now requires the tftp package where suse_version is set. That is the
hpa server, and it listens on 0.0.0.0:69 and [::]:69 at once. EL keeps the file
dependency, which has one provider there, tftp-server.

Measured on a Leap 15.6 management node: with atftp the loader could not be
fetched over IPv6 and could over IPv4; after the swap both families served the
same 1372160 byte loader, and a missing file still answered File Not Found.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-28 12:03:56 -03:00