diff options
| author | Craig Jennings <c@cjennings.net> | 2026-06-25 12:21:15 -0400 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-06-25 12:21:15 -0400 |
| commit | 9a0b4bbbcb5ff05bc578eff07af27c08a03f7f59 (patch) | |
| tree | 549f6702cbb5b4c8668f4c7aadb881b9a4428527 /scripts/testing/tests/test_config_applied.py | |
| parent | 9feb5faf93cb15be7ba77ad72a92e191cd66045a (diff) | |
| download | archsetup-9a0b4bbbcb5ff05bc578eff07af27c08a03f7f59.tar.gz archsetup-9a0b4bbbcb5ff05bc578eff07af27c08a03f7f59.zip | |
test(archsetup): add FS_PROFILE selector for ZFS VM coverage
The VM harness only built one btrfs base image, so every ZFS-conditional check in the Testinfra suite skipped and the ZFS install path went untested in automation. I added an FS_PROFILE selector (btrfs default, zfs) so `make test FS_PROFILE=zfs` can target a ZFS root.
init_vm_paths derives the image name from FS_PROFILE and validates it. btrfs keeps the legacy unsuffixed archsetup-base.qcow2 so existing images and invocations are untouched. The zfs profile gets archsetup-base-zfs.qcow2. create-base-vm.sh picks archsetup-test.conf vs the new archsetup-test-zfs.conf (FILESYSTEM=zfs, NO_ENCRYPT=yes for an unattended install), and the Makefile resolves the matching image for its base-VM check.
The archsetup run config stays shared. archsetup reads no filesystem key. It detects ZFS from the live root via is_zfs_root, so the ZFS branch fires on its own once the base image is ZFS. The design doc is reconciled to that: no separate archsetup-vm-zfs.conf, and the non-ZFS profile is btrfs, not ext4.
Building the ZFS base image and running the ZFS sweep green is next.
Diffstat (limited to 'scripts/testing/tests/test_config_applied.py')
0 files changed, 0 insertions, 0 deletions