diff options
| author | Craig Jennings <c@cjennings.net> | 2026-06-25 19:52:46 -0400 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-06-25 19:52:46 -0400 |
| commit | b15c0e17d73611d0d70dd830f2af7a95aeeb919e (patch) | |
| tree | 4d6357e82e438f85c81cfc5f1f7c1ba9381b6cdb /scripts/testing/archsetup-vm.conf | |
| parent | 8f32ec75fde2868f27d04eac3e0a374910ed8701 (diff) | |
| download | archsetup-b15c0e17d73611d0d70dd830f2af7a95aeeb919e.tar.gz archsetup-b15c0e17d73611d0d70dd830f2af7a95aeeb919e.zip | |
test(archsetup): branch boot/backup checks on the ZFS boot path
The Testinfra boot and backup checks asserted btrfs behavior unconditionally, so they failed on a ZFS root once the ZFS VM path started running them. ZFS boots via ZFSBootMenu, not GRUB. archsetup skips the systemd-hook switch and the mkinitcpio rebuild on ZFS, and on a ZFS+virtio VM it never edits mkinitcpio.conf at all. Branch each check on the existing zfs_root/has_nvme fixtures: assert the ZFSBootMenu EFI binary on ZFS (GRUB on btrfs), gate the mkinitcpio.conf backup on archsetup actually editing the file, and check the console font in /etc/vconsole.conf on ZFS (the initramfs on non-ZFS).
Surfaced by the first full ZFS VM run, which completed archsetup cleanly (exit 0). These were the only 3 failures.
Diffstat (limited to 'scripts/testing/archsetup-vm.conf')
0 files changed, 0 insertions, 0 deletions