mirror of
https://github.com/xcat2/xcat-core.git
synced 2026-10-02 08:51:44 +00:00
Daniel Hilst
28dc05c226
servicenode.nfsserver=1 asks a service node to set up file services for the nodes behind it. With site.installloc set, AAsn.pm mounts the install directory from the management node and exports nothing, and setup_NFS only starts the daemon, so the service node serves no NFS at all. Only the branch where installloc is unset ever wrote an export. An Ubuntu compute node boots the live installer with casper, which mounts the install tree over NFS from its own service node. Measured on xcat22-cn: the boot arguments carried nfsroot=192.168.222.21:/install/ubuntu24.04.4/x86_64, and the node stopped at "(initramfs) Unable to find a live file system on the network". On xcat22-sn, showmount -e returned an empty list and /etc/exports was empty while nfs-kernel-server was active. EL never needed this, because anaconda fetches over http. setup_NFS now exports the install directory when nothing exports it yet, then runs exportfs after the daemon. Re-exporting an NFS mount is not the same as exporting a local directory: the kernel cannot derive a filesystem id for one and refuses the export without an explicit fsid, so nfs_export_line adds fsid and crossmnt when the directory is itself a mount. The fsid comes from the path, so a restart does not hand clients a new filesystem identity. An export the kernel refuses is reported and does not fail the service node. The EL cell is re-run on this tree, because an EL service node now writes an export it did not write before. svrutils_nfs_export_line.t drives the routine. Five mutations were tried and each one fails the assertions that name it. 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 |
| 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.
See unit/README.md and bats/README.md for the detailed rules for
each unit-test suite.