View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004555 | Rocky-Linux-8 | osbuild | public | 2023-10-22 15:55 | 2023-10-22 16:06 |
| Reporter | Daniel Milnes | Assigned To | |||
| Priority | normal | Severity | crash | Reproducibility | always |
| Status | new | Resolution | open | ||
| Summary | 0004555: Building Rocky 8 images calls Rocky 9 target and fails | ||||
| Description | It appears to currently be impossible to build a Rocky 8 image using osbuild. On a fresh install of Rocky 8 with a very simple template, osbuild tries to run a rocky9 osbuild step. It can't find this step within the bwrap environment, so the build fails. I believe this is related to Rocky's patchset, as I cannot replicate this issue on RHEL 8.8. To test this, replace the `distro` with `rhel-88`. Attaching strace to the worker does not appear to provide any additional information. | ||||
| Steps To Reproduce | 1. Set up Rocky 8.8 2. Install osbuild dnf install osbuild-composer composer-cli -y 3. Start osbuild systemctl enable --now osbuild-local-worker.socket systemctl enable --now osbuild-composer.socket 4. Submit the blueprint attached to this ticket composer-cli blueprints push <path> 5. Start a build composer-cli compose start rocky-8-base qcow2 --size 20000 6. Watch the journal and wait for the exception osbuild-worker[29124]: time="2023-10-22T15:42:19Z" level=info msg="build pipeline results:\n" jobId=40174b1f-1076-441b-a529-fed2ae190d1b osbuild-worker[29124]: time="2023-10-22T15:42:19Z" level=info msg=" org.osbuild.rpm failure:" jobId=40174b1f-1076-441b-a529-fed2ae190d1b osbuild-worker[29124]: time="2023-10-22T15:42:19Z" level=info msg=" bwrap: execvp /run/osbuild/runner/org.osbuild.rocky9: No such file or directory" jobId=40174b1f-1076-441b-a529-fed2ae190d1b osbuild-worker[29124]: time="2023-10-22T15:42:19Z" level=info msg=" " jobId=40174b1f-1076-441b-a529-fed2ae190d1b osbuild-worker[29124]: time="2023-10-22T15:42:19Z" level=error msg="osbuild job failed: osbuild build failed" jobId=40174b1f-1076-441b-a529-fed2ae190d1b osbuild-worker[29124]: time="2023-10-22T15:42:19Z" level=info msg="Job '40174b1f-1076-441b-a529-fed2ae190d1b' (osbuild) finished" | ||||
| Additional Information | Package versions: # rpm -qa | grep osbuild osbuild-composer-dnf-json-75-1.el8.rocky.0.2.x86_64 python3-osbuild-81-1.el8.rocky.0.2.noarch osbuild-lvm2-81-1.el8.rocky.0.2.noarch osbuild-composer-core-75-1.el8.rocky.0.2.x86_64 osbuild-selinux-81-1.el8.rocky.0.2.noarch osbuild-luks2-81-1.el8.rocky.0.2.noarch osbuild-ostree-81-1.el8.rocky.0.2.noarch osbuild-composer-75-1.el8.rocky.0.2.x86_64 osbuild-81-1.el8.rocky.0.2.noarch osbuild-composer-worker-75-1.el8.rocky.0.2.x86_64 OSBuild Blueprint: name = "rocky-8-base" version = "1.0.0" distro = "rocky-88" groups = [ { name = "Core" }, ] | ||||
| Tags | No tags attached. | ||||
 |
Additionally, this bug does not appear to be present building Rocky 8 from Rocky 9. This is especially weird, as the patch that adds Rocky 8 support is common between releases (https://git.rockylinux.org/staging/rpms/osbuild-composer/-/blob/r9/SOURCES/0001-Add-Rocky-Linux-8-and-9-Support.patch?ref_type=heads). |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-10-22 15:55 | Daniel Milnes | New Issue | |
| 2023-10-22 16:06 | Daniel Milnes | Note Added: 0004951 |
