f4f0c8f004
With lvm2 the generated fedora fc38 boot image boots in degraded mode with the following error: ``` [root@localhost ~]# journalctl -u lvm2-monitor.service|more Nov 13 12:52:04 localhost.localdomain lvm[431]: Failed to create /etc/lvm/devi ces 2 Nov 13 12:52:04 localhost.localdomain lvm[431]: Failed to set up devices. Nov 13 12:52:04 localhost.localdomain systemd[1]: lvm2-monitor.service: Main pro cess exited, code=exited, status=5/NOTINSTALLED Nov 13 12:52:04 localhost.localdomain systemd[1]: lvm2-monitor.service: Failed w ith result 'exit-code'. Nov 13 12:52:04 localhost.localdomain systemd[1]: Failed to start lvm2-monitor.s ervice - Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress p olling. ``` This breaks the `test_boot.py` which expects the system after booting in `running` state (from `systemd is-system-running`). It looks like this is some sort of race with our generated image, potentially related to selinux, see https://github.com/lvmteam/lvm2/blob/v2_03_18/lib/device/dev-cache.c#L1842 and note the lines around dm_prepare_selinux_context(). Note also that `lvm2-monitor.service` runs with `DefaultDependencies=no` (c.f. https://github.com/lvmteam/lvm2/blob/v2_03_18/scripts/lvm2_monitoring_systemd_red_hat.service.in#L7) Given that the official fc38 cloud image does not use lvm2 and that it's not needed for the boot test this commit simply removes it from the fedora-boot manifest. This fixes the test. |
||
|---|---|---|
| .. | ||
| cases | ||
| data | ||
| mod | ||
| run | ||
| .gitignore | ||
| __init__.py | ||
| conftest.py | ||
| initrd.py | ||
| test.py | ||