osbuild-composer
osbuild-composer copied to clipboard
iso built with edge-installer option can not boot
Describe the bug I followed the instructions here to build an Edge installer image from an edge commit. The resulting installer does not boot.
I am running Centos Stream 9 and have installed osbuild and osbuild-composer from their respective copr's to play with container image embedding. I tried booting the installer image in a VM and the installer fails to boot. I'm not sure if this a bug here or in Anaconda, and if this is the wrong place, please let me know.
Environment
- OS version (
/etc/os-release
and/etc/redhat-release
):
$ cat /etc/os-release
NAME="CentOS Stream"
VERSION="9"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="9"
PLATFORM_ID="platform:el9"
PRETTY_NAME="CentOS Stream 9"
ANSI_COLOR="0;31"
LOGO="fedora-logo-icon"
CPE_NAME="cpe:/o:centos:centos:9"
HOME_URL="https://centos.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux 9"
REDHAT_SUPPORT_PRODUCT_VERSION="CentOS Stream"
$ cat /etc/redhat-release
CentOS Stream release 9
- osbuild-composer version (
rpm -qi osbuild-composer)
$ rpm -qi osbuild-composer
Name : osbuild-composer
Version : 59
Release : 1.20220811162110105448.main.5.g6e771c97.el9
Architecture: x86_64
Install Date: Thu 11 Aug 2022 07:42:44 PM EDT
Group : Unspecified
Size : 17612
License : ASL 2.0
Signature : RSA/SHA256, Thu 11 Aug 2022 01:47:34 PM EDT, Key ID 3b00c986c7061f69
Source RPM : osbuild-composer-59-1.20220811162110105448.main.5.g6e771c97.el9.src.rpm
Build Date : Thu 11 Aug 2022 12:36:41 PM EDT
Build Host : aws-x86-64-spot-prod-01995951-20220811-162903
Vendor : Fedora Copr - group @osbuild
URL : https://github.com/osbuild/osbuild-composer
Summary : An image building service based on osbuild
Description :
A service for building customized OS artifacts, such as VM images and OSTree
commits, that uses osbuild under the hood. Besides building images for local
usage, it can also upload images directly to cloud.
It is compatible with composer-cli and cockpit-composer clients.
To Reproduce Steps to reproduce the behavior:
- Build an
edge-installer
following the instructions here - Download the image.
- Create a new VM in virt-manager and select the downloaded ISO as the installation source. Make sure to select UEFI for the boot type.
- Wait for the installer boot.
Expected behavior The installer to finish booting and to be greeted by an Anaconda window to make selections in.
Additional context
I believe this is the relevant part of the error message that appeared when the installer failed to boot.
What does the output from 'cat /proc/cmdlineand
blkid` look like? The cmdline will have the label that dracut is looking for, and blkid will show the labels of the mounted devices.
Where would I run that at?
From the cmdline after the failure to boot, it might take a bit for dracut to time out, but eventually there should be a bash shell available for debugging.
Ahhh. I'll take a look a little later this week.
I replicated the problem with an image-installer
type instead of an edge-installer
.
The output of cat /proc/cmdline
and blkid
in the VM I'm trying to boot is below.
For consistency:
Name : osbuild-composer
Version : 59
Release : 1.20220816153002551242.main.7.g239e8ccb.el9
Architecture: x86_64
Install Date: Tue 16 Aug 2022 05:57:50 PM EDT
Group : Unspecified
Size : 17612
License : ASL 2.0
Signature : RSA/SHA256, Tue 16 Aug 2022 11:45:12 AM EDT, Key ID 3b00c986c7061f69
Source RPM : osbuild-composer-59-1.20220816153002551242.main.7.g239e8ccb.el9.src.rpm
Build Date : Tue 16 Aug 2022 11:33:31 AM EDT
Build Host : copr-hv-x86-64-04-prod-02020720-20220816-152726
Vendor : Fedora Copr - group @osbuild
URL : https://github.com/osbuild/osbuild-composer
Summary : An image building service based on osbuild
Description :
A service for building customized OS artifacts, such as VM images and OSTree
commits, that uses osbuild under the hood. Besides building images for local
usage, it can also upload images directly to cloud.
It is compatible with composer-cli and cockpit-composer clients.
The image was build using the blueprint:
name = "empty"
description = "An empty image."
version = "0.0.0"
using the compose command:
composer-cli compose start empty image-installer
I then downloaded the iso from composer and tried booting it with virt-manager.
Thanks for reporting this, we already know about the image-installer
issue and we're working on fixing it. It seems to be caused by dracut nvmf
module, when removed the iso boots, but we need to verify if the original http boot issue fix will stay unaffected, there seems to be a grub bug that's making the verification difficult though.