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>
xCAT-test
Unit tests that run from the source checkout are split by implementation language:
| Test type | Location | Runner |
|---|---|---|
| Perl unit tests | xCAT-test/unit/*.t |
prove -r xCAT-test/unit |
| Shell unit tests | xCAT-test/bats/*.bats |
bats -r xCAT-test/bats |
| Black-box service tests | xCAT-test/blackboxtest/ |
python3 -m unittest discover -s tests, then blackboxtest run <conf> on a management node |
| Native host tests | xCAT-test/native/*.t, xCAT-test/native/*.bats |
Selected CI cases and explicit lab runs; see native/README.md |
| CLI functional tests | xCAT-test/autotest/testcase/ and xCAT-test/autotest/bundle/ |
xcattest -f <cluster.conf> -t <case> or xcattest -f <cluster.conf> -b <bundle> |
Use Perl .t tests for Perl modules, Perl scripts, templates, and repository
artifacts. Use BATS tests for shell-script behavior that can be exercised from
the checkout by sourcing a shell library or script and shadowing external
commands.
Shell behavior should not be tested by Perl tests that grep shell source. Put
those tests under xCAT-test/bats instead.
blackboxtest is the odd one out: its Python unit tests and blackboxtest validate run offline like the others, but its point is the third column --
asking a management node what a booting node asks (DHCP, DNS, TFTP, HTTP,
xcatd) and asserting on the answers. It talks to the services only as a client,
so it does not depend on which DHCP server answers or on the xCAT database.
See unit/README.md, bats/README.md and blackboxtest/README.md for the
detailed rules for each suite.