Daniel HilstNative host tests
These tests use the source checkout with RPM tools, Linux namespaces or real
service binaries. They are separate from unit/ and are not discovered by the
default pull-request unit run. Run them explicitly on a disposable Linux host.
The postinstall case requires bubblewrap and the Perl modules used by the xCAT template renderer. It runs complete rendered installer and postboot scripts in private filesystems, with doubles for downloads and service commands:
prove xCAT-test/native/postinstall_bootstrap.t
It can run as root or an ordinary user with user namespaces enabled. This case checks service policy and ordering; it does not boot or reinstall an OS. The client steps cannot access the source tree or the server postscripts directory.
Ubuntu media and image fixtures
The pull-request workflow runs these four tests explicitly:
prove xCAT-test/native/ubuntu_live_media_guardrails.t \
xCAT-test/native/ubuntu_genimage_debootstrap_arch.t \
xCAT-test/native/ubuntu_genimage_apt_mirror.t \
xCAT-test/native/ubuntu_genimage_resolver_libs.t
They require Linux user namespaces, Bubblewrap, cpio, gzip, GNU timeout and
the system Perl in /usr/bin or /bin. Install the source-tree Perl dependencies,
including File::Slurper, DBI and DBD::SQLite, for that interpreter. Tools must be
in /usr/bin, /bin, /usr/sbin or /sbin. Run the tests as an ordinary user.
Missing Linux prerequisites fail the tests; other operating systems skip them.
The fixtures execute the checkout's unchanged Debian plugin and Ubuntu genimage script with private filesystems and no network access. Media copying, database updates, the image's APT sources.list and initrd archives are real. Decompression and archive inspection are real too. The debootstrap command records its arguments; the architecture test stops at its deliberate failure. The mirror test lets it complete, replaces mount commands and stops at a deliberate apt-get update failure. The initrd fixture supplies chroot ldd and depmod results. These tests do not install packages, execute target-architecture binaries or prove that the generated image boots.
Other native tests
Run the package and unprivileged namespace cases as an ordinary user:
prove xCAT-test/native/buildrpms_openeuler.t \
xCAT-test/native/buildrpms_release_openeuler.t \
xCAT-test/native/genesis_openeuler*.t \
xCAT-test/native/openeuler_genimage_bootfiles.t \
xCAT-test/native/openeuler_package_policy.t
Run the isolated system cases as root:
sudo prove xCAT-test/native/ip_forwarding.t \
xCAT-test/native/openeuler_genimage_transactions.t \
xCAT-test/native/openeuler_install_repositories.t \
xCAT-test/native/openeuler_networking.t \
xCAT-test/native/openeuler_xcatroot.t \
xCAT-test/native/remoteshell_hostkeys_openeuler.t \
xCAT-test/native/syslog_openeuler*.t
The PostgreSQL case starts a private server with only a Unix socket. Run it as
an ordinary user with XCAT_TEST_PG_BINDIR set to the directory containing
initdb, pg_ctl, postgres, psql and createdb:
XCAT_TEST_PG_BINDIR=/usr/bin prove xCAT-test/native/pgsqlsetup_native_schema.t
Check the TAP output for skipped prerequisites. A successful prove exit with
skipped cases does not qualify those cases.
Package lifecycle
Run these cases as an ordinary user with unprivileged Linux namespaces enabled. They use private filesystem, process and network namespaces, not host services.
On Debian or Ubuntu, install bubblewrap, debhelper, devscripts, fakeroot,
quilt, ucf, debconf-utils, systemd, rpm, apache2, curl,
libcapture-tiny-perl and libfile-slurper-perl, then run:
prove xCAT-test/native/xcatd_debian_lifecycle.t \
xCAT-test/native/xcatd_restart_callers.t \
xCAT-test/native/apache_package_lifecycle.t \
xCAT-test/native/package_upgrade_logging.t
On EL8 or EL10, install bubblewrap, rpm-build, systemd, chkconfig,
initscripts, httpd, curl, tar, gzip, which, diffutils, procps-ng,
perl-Capture-Tiny, perl-File-Slurper and perl-Test-Simple, then run:
prove xCAT-test/native/xcatd_rpm_lifecycle.t \
xCAT-test/native/apache_rpm_configuration.t \
xCAT-test/native/apache_package_lifecycle.t \
xCAT-test/native/package_upgrade_logging.t
These EL dependencies need EPEL plus PowerTools on EL8 or CRB on EL10.
Package transactions use native package tools and private package databases. Dependency resolution is bypassed to isolate maintainer-script behavior. Service registration uses real offline tools. Service dispatch uses command fixtures, while header checks start real Apache on an isolated loopback port. The service cases execute the installed unit's start command with a daemon fixture. RPM upgrades also cover the old package-owned init-script layout. The Debian Apache cases unpack built packages and execute their complete maintainer scripts. Restart-caller cases execute complete Debian scripts and RPM-rendered scriptlets without building the optional UI package.
Upgrade logging cases run package transactions with a configuration-command
fixture. They check output, warnings, PID relocation, temporary files and the
different RPM and Debian failure policies. They do not run xcatconfig or
build a Genesis image.
The RPM Apache cases distinguish a root without /proc from a chroot with
/proc mounted and a different PID 1 root. Debian and restart-caller cases
check dispatch with and without /proc; these do not qualify chroot safety.
The configuration cases exercise EL and SUSE build-macro selections on native EL RPM tools. The legacy release identities select init policy, not a native EL6 or Ubuntu 14.04 environment. These cases do not qualify native SUSE package transactions, dependency resolution, a running xcatd daemon, or machine boot. The namespace fixture targets merged-/usr hosts. Container runs need namespace permissions and an init process that reaps orphaned children.
Genesis OpenEmbedded
genesis_metadata.py runs inside a Genesis KAS shell. It uses BitBake to
evaluate machine and package policy, install local-file recipes into temporary
directories, generate extension manifests and reject invalid extension
metadata. It does not extract or evaluate recipe source fragments.
For example, from the source checkout:
export KAS_WORK_DIR=/path/to/kas-work
export KAS_BUILD_DIR=/path/to/kas-build-x86_64
source_tree=$PWD
kas dump --format json xCAT-genesis-base/oe/kas/x86_64.yml >"${KAS_BUILD_DIR}.json"
kas shell xCAT-genesis-base/oe/kas/x86_64.yml -c \
"GENESIS_ARCHITECTURE=x86_64 GENESIS_KAS_CONFIG='${KAS_BUILD_DIR}.json' python3 '${source_tree}/xCAT-test/native/genesis_metadata.py'"
Use the pinned KAS requirements and OpenEmbedded host prerequisites from
xCAT-genesis-base/oe. Run as an ordinary user with an executable temporary
directory. BitBake's build directory must use a supported local filesystem.
The genesis_openembedded workflow runs the metadata tests for x86, x86_64,
ppc64, ppc64le, armv7hf, aarch64, riscv64 and s390x.
python3 xCAT-test/native/genesis_console.py builds and installs the complete
console with Meson, then runs the installed program. It requires a C compiler,
Meson, Ninja, pkg-config, and development packages for Newt and systemd.
The unit test retains checks of the vendored release key, requested kernel fragments and console service configuration. The BATS tests retain runtime, console, hardware and packet behavior. None of these checks replaces a full image build, inspection of its resolved kernel configuration or a boot test.