Daniel Hilst
a5cc24c18f
DHCP backend auto-selection fails hard when the backend it prefers is not installed. The xcat metapackage's "isc-dhcp-server | kea" Depends guarantees isc-dhcp-server, while auto-selection prefers kea on 22.04+, where kea arrives only through Recommends. An apt run that skips recommends therefore leaves a node with isc only, auto picks the absent kea, and makedhcp errors out on a freshly installed management node (#7710). makedhcp -q re-enters omshell on the very releases whose write paths avoid it. xCAT already records each reservation as a static host block in dhcpd.conf on Ubuntu's ISC-limited releases because their ISC DHCP 4.4 omshell can wedge at 100% CPU and never be reaped, but listnode still called _omshell_query_host unconditionally. Both host-block scans also match the node name loosely: /\Q$node\E\b.* start$/ matches at a hyphen, so "compute" matches the "compute-01" marker -- a query can answer with another node's address and a delete can remove another node's reservation. Cover all three: the auto-selection fallback, a query answered from dhcpd.conf without omshell, and exact node-name matching for both the query and the delete. 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.
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.