The OpenEmbedded Genesis image ships one NetworkManager configuration, 10-xcat-genesis.conf, and it sets ipv6.dhcp-duid=ll. The image therefore sends the DUID-LL of the provisioning NIC. makedhcp reserves the two DUID-UUID orders that EDK2 and iPXE send, or a DUID-LL when mac.duid asks for one, and the two forms are exclusive. No test says which identities one node needs, so a reservation set that answers the firmware and the loader and not the image passes. The new block renders the Kea DHCPv6 reservations of a netboot=ipxe node and asserts the DUIDs, which client keeps the address and the hostname, and the boot file URL of each. It asserts the same node on ISC DHCP and through makedhcp -d, and that mac.duid=ll, a literal DUID and the DHCPv4 reservations are unchanged. Ten assertions fail on this commit: the DUID-LL is reserved nowhere. 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.