reg_linux_diskless_installation_flat fails on every ppc64le cell. rpower boot leaves the compute node down and libvirt reports "unsupported configuration: Emulator '/usr/bin/qemu-system-ppc64' does not support machine type 'pseries-rhel7.6.0'". vm_machine_type_for_arch in vm_machine_type.sh answered machine:pseries-rhel7.6.0 for every ppc64 architecture. The ppc64le hypervisor runs AlmaLinux 10, whose qemu-system-ppc64 declares pseries-5.0 to pseries-10.2 and no rhel machine type, so the name the case writes cannot be defined there. The function now reads the vmhost of the node and asks that host's libvirt. It writes the plain alias when libvirt accepts it, that libvirt's own default when it does not, and the alias when the vmhost cannot be asked. x86_64 keeps machine:pc, which is an alias and stays valid. xCAT-test/bats/vm_machine_type.bats covers it. Nine of its tests fail on the previous commit, among them "the vmhost accepts the machine type that comes back" and "the machine type is the alias the vmhost accepts". 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.