A node solicits over DHCPv6 under more than one DUID, and kea_node_reservations6 reserved the address for the first client only. The OpenEmbedded Genesis image sends the DUID-UUID in the order the firmware sends, which is not that client, so it took an address from the dynamic range. xcatd could not map the address to a node, Genesis reported CERTIFICATE_ACTION_FAILED with the node unassigned, and discovery over IPv6 stopped there. Which order the firmware sends is not the same on every platform. For a KVM guest getNodeUUID writes the byte swap of vpd.uuid into the domain, and the firmware swaps those bytes back, so the order the firmware sends is the one the code labels for iPXE. makedhcp now gives a node of several clients a pool of exactly its address, gated on a client class that matches every DUID of the node, and leaves the address out of the reservation: Kea excludes a reserved address from every pool. The reservation still carries the hostname, on one entry, because _reservation_matches treats a shared hostname as the same reservation. A node with one client is unchanged and keeps its address in its reservation. dhcp_dhcpv6_duid.t reads the address through the pool as well as the reservation. Without the pool insertion its nine address assertions fail. 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.