On ISC DHCP a KVM guest that xCAT defines and that netboots with ipxe boots neither stage: the firmware receives the iPXE boot script and iPXE receives the shim. addnode6 and addnode6_other_clients chose the boot file of each DHCPv6 host from the client label of its DUID. The label follows from vpd.uuid, but which UUID order the firmware sends depends on the UUID of the libvirt domain. For a guest that mkvm defines the labels are reversed. The two hosts that hold a UUID order of a chainloading node now carry one statement that chooses the file by boot stage: the boot script when option 15, the User Class, holds iPXE, and the shim otherwise. The Kea classes from kea_node_boot_classes6 make the same split. isc_dhcp6_boot_stage_statement in BootPolicy builds the statement. dhcp_dhcpv6_duid.t asserts the statement on both hosts of a KVM node. The assertions fail without this change. Two older assertions expected one file per label and now expect the statement. 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.