A DHCPv6 reservation is keyed on the DUID, and a DUID names the machine, not the nic. 10-xcat-genesis.conf puts the DHCPv6 settings in [connection], which NetworkManager applies to every nic, so each nic of a node asks for the same reserved address and Kea gives it to the first REQUEST. Measured on xcat88-cn, which carries three nics on the provisioning bridge virbr-p88. Kea logged four solicits under one DUID in one boot, and granted 2001:db8:188::20 to whichever IA asked first; the others took pool addresses. The node then reported to xcatd from an address xcatd could not match to a node, so el10-x86_64-genesis-oe-ipv6 passed or failed by chance. genesis-bootnic reads BOOTIF and writes 16-xcat-genesis-bootnic.conf, which leaves DHCPv6 on the boot nic and puts every other nic on link-local. It follows genesis-duid, which already writes 15-xcat-genesis-duid.conf from the SMBIOS UUID before NetworkManager starts. The six cases pass with the file as committed, so the evidence is a mutation: writing ipv6.method=auto for the secondary nics, which is the behaviour before this change, reds only "the boot nic keeps DHCPv6 and every other nic does not ask for an address". 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.