selinux_cn_diskless_disabled_by_design looks for the boot configuration of the compute node in three places: the xnba node directory, pxelinux.cfg by node name, and petitboot. A node with netboot=ipxe has its script in /tftpboot/xcat/ipxe/nodes/<node>.uefi instead, which the list does not name, so the case reports BOOTCFG-BAD: the node has no boot configuration BOOTCFG-BAD: no boot configuration carries selinux=0 and fails on every iPXE cell. xcat54-cn of el10-x86_64-devel is netboot=ipxe, so build 78 of xcat-test-el10-x86_64 failed there after its other checks passed: the node reported SELinux disabled and the case still could not confirm the flag reached the boot configuration. Both path lists now name the iPXE script, the UEFI one first, which is the file a UEFI client fetches. nodeset/ipxe_secureboot_shim.sh already reads that path. The paths stay absolute, so the check still fails when no boot configuration carries selinux=0. 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.