Daniel Hilst
4a8877618a
reg_linux_diskfull_installation_flat fails on ubuntu-22-ppc64le-devel and ubuntu-24-ppc64le-devel in build #121 of xcat-core-devel-ubuntu-cd. The node answers ping but the case ends on "root@xcat25-cn: Permission denied (publickey,password)" and the node status never leaves powering-on. The serial console shows why: the Subiquity installer starts, runs the early-commands, errors, tars /var/log/installer to port 8080 and reboots. Nine cycles in 75 minutes. The installed system never exists, so the address belongs to the live installer and it refuses the root key. Two causes, both POWER-only. mkinstall picks pre.ubuntu.subiquity, then overwrites that choice with pre.ubuntu.ppc64 for every ppc64 node. That script writes a partman recipe; the early-commands append it to /autoinstall.yaml, which Subiquity then cannot parse. pre.ubuntu.subiquity has a UEFI branch and a BIOS branch and nothing else, so a ppc64el node takes the BIOS branch and is given a bios_grub partition. POWER firmware boots from a PReP partition. debian_install_prescript.t drives the script choice, which mkinstall keeps inline, so it bails out. ubuntu_subiquity_storage.t gains a PReP case; its extracted block asks uname for the machine architecture, which the block does not do yet. Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
xCAT-test/unit
Unit tests. These run against the source tree only -- no xCAT installation, no running daemons, no management node.
They are executed on every pull request by the xcat_test GitHub Actions workflow,
which calls run_unit_tests() in github_action_xcat_test.pl:
prove -r xCAT-test/unit
You can run exactly the same thing from a clean checkout:
cd <xcat-core checkout>
prove -r xCAT-test/unit
What belongs here
A test belongs in unit/ when everything it needs is in the checkout: plugin and
library sources, kickstart/preseed/subiquity templates, postscripts, packaging
metadata. Such a test asserts on rendered output or module logic and reaches the
repository root through FindBin:
use FindBin;
use lib "$FindBin::Bin/../../perl-xCAT";
use lib "$FindBin::Bin/../../xCAT-server/lib/perl";
Because of those FindBin paths the tests only work from a source tree. The copy
installed under /opt/xcat/share/xcat/tools/autotest/unit is not a substitute --
../.. resolves to /opt/xcat/share/xcat/tools there and the tests die or silently
skip. The CI takes a copy of the checkout before the build for this reason; see
preserve_source_tree().
What does not belong here
Anything that needs an installed xCAT, a populated /install, a real service binary
or a live daemon. Those go in ../integration and run on
a management node through xcattest. Both suites run on every pull request -- the
workflow installs xCAT on the runner and then runs the ci_test cases against it --
so putting a test in integration/ does not cost it CI coverage. What differs is what
each suite is allowed to depend on, and that unit tests also run standalone from a
bare checkout with no xCAT at all.
Shell-script unit tests belong in ../bats
and run with BATS. Do not add Perl .t tests that grep shell source when the
behavior can be exercised by sourcing a shell library or script and shadowing the
external commands it calls.
The distinction matters because a test that needs an absent environment does not fail
-- it calls plan skip_all and reports as skipped. A handful of those in a suite of
several hundred assertions is easy to stop reading. Keeping the two kinds in separate
directories means a skip in unit/ is a real signal rather than routine noise.
Guarding on a source file, on the other hand, is fine and common here:
plan skip_all => "compute.subiquity.tmpl not found" unless -f $tmpl_path;
That guard never fires when the tree is intact.