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. |
||
|---|---|---|
| .devcontainer | ||
| .github | ||
| assemblers | ||
| data | ||
| devices | ||
| docs | ||
| inputs | ||
| mounts | ||
| osbuild | ||
| runners | ||
| schemas | ||
| schutzbot | ||
| selinux | ||
| sources | ||
| stages | ||
| test | ||
| tools | ||
| .bandit | ||
| .editorconfig | ||
| .git-blame-ignore-revs | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .mypy.ini | ||
| .packit.yaml | ||
| .ruff.toml | ||
| LICENSE | ||
| Makefile | ||
| osbuild.spec | ||
| README.md | ||
| requirements.txt | ||
| samples | ||
| Schutzfile | ||
| setup.cfg | ||
| setup.py | ||
| tox.ini | ||
OSBuild
Build-Pipelines for Operating System Artifacts
OSBuild is a pipeline-based build system for operating system artifacts. It defines a universal pipeline description and a build system to execute them, producing artifacts like operating system images, working towards an image build pipeline that is more comprehensible, reproducible, and extendable.
See the osbuild(1) man-page for details on how to run osbuild, the definition
of the pipeline description, and more.
Project
- Website: https://www.osbuild.org
- Bug Tracker: https://github.com/osbuild/osbuild/issues
- Matrix: #image-builder on fedoraproject.org
- Mailing List: image-builder@redhat.com
- Changelog: https://github.com/osbuild/osbuild/releases
Contributing
Please refer to the developer guide to learn about our workflow, code style and more.
Requirements
The requirements for this project are:
bubblewrap >= 0.4.0python >= 3.6
Additionally, the built-in stages require:
bash >= 5.0coreutils >= 8.31curl >= 7.68qemu-img >= 4.2.0rpm >= 4.15tar >= 1.32util-linux >= 235skopeo
At build-time, the following software is required:
python-docutils >= 0.13pkg-config >= 0.29
Testing requires additional software:
pytest
Installation
Installing osbuild requires to not only install the osbuild module, but also
additional artifacts such as tools (i.e: osbuild-mpp) sources, stages, schemas
and SELinux policies.
For this reason, doing an installation from source is not trivial and the easier way to install it is to create the set of RPMs that contain all these components.
This can be done with the rpm make target, i.e:
make rpm
A set of RPMs will be created in the ./rpmbuild/RPMS/noarch/ directory and can
be installed in the system using the distribution package manager, i.e:
sudo dnf install ./rpmbuild/RPMS/noarch/*.rpm
Repository
- web: https://github.com/osbuild/osbuild
- https:
https://github.com/osbuild/osbuild.git - ssh:
git@github.com:osbuild/osbuild.git
License
- Apache-2.0
- See LICENSE file for details.