Bug 2128798

Summary:	When building a RHEL ISO, "Kickstart is insufficient"
Product:	Red Hat Enterprise Linux 8	Reporter:	Christophe Besson <cbesson>
Component:	osbuild-composer	Assignee:	Image Builder team <osbuilders>
Status:	CLOSED MIGRATED	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.6	CC:	albert.campanya.soler, bugzilla.redhat, rmetrich, sbarcomb, thozza
Target Milestone:	rc	Keywords:	MigratedToJIRA, Reproducer, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-18 13:16:30 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Christophe Besson 2022-09-21 14:10:26 UTC

Description of problem:
Using Image Builder to generate an ISO leads to a "Kickstart is insufficient" message in the GUI.

It seems the installation_device directive (mentioned only in the Edge section of the doc) does not work.
The user has been added to the KS, locale (TZ, lang, KB) has been included directly in the tarball, but the FS customizations are not taken into account.

Version-Release number of selected component (if applicable):
osbuild-composer-46.3-1.el8_6.x86_64
osbuild-53-2.el8.noarch

How reproducible:
Always

Steps to Reproduce:
1. Use a blueprint with below customization settings
[customizations]
hostname = "golden-image-rhel86"
installation_device = "/dev/sda"

[[customizations.user]]
name = "postinstall"
description = "postinstall"
password = "redhat01"
groups = ["wheel"]
[customizations.timezone]
timezone = "Europe/Brussels"
[customizations.locale]
languages = ["en_US.UTF-8"]
keyboard = "be-latin1"
[customizations.firewall]
ports = ["22:tcp"]
[customizations.services]
enabled = ["sshd"]

[[customizations.filesystem]]
mountpoint = "/"
size = 8589934592

[[customizations.filesystem]]
mountpoint = "/var"
size = 5368709120

2. Generate an ISO 
# composer-cli compose start rhel86-iso image-installer

3. Install the ISO (s/sda/vda/ if running in qemu-kvm)

Actual results:
"Kickstart is insufficient" in the GUI (under the disk section).

osbuild.ks content:

liveimg --url file:///run/install/repo/liveimg.tar
user --name postinstall --password $6$GX1QdzFs13w5V22o$srZjjJSNsli38t1Fs92FOBqOvMCqCFtFPRGTk8aT4O73vcVIL8J2MtyCKfhLKKsEZjCtEMnnAbTEC5LAkgbzN0 --iscrypted --groups wheel

Expected results:
Take into account all the customizations or warn if it is not taken into account for a given image type.

Additional info:
- Upstream issue (which also reports network should be enabled on boot):
https://github.com/osbuild/osbuild-composer/issues/2255

Comment 1 Dagan McGregor 2023-05-01 23:54:20 UTC

I have run into this same problem creating an ISO file through the Red Hat hosted image builder in the customer console.

# cat osbuild.ks
liveimg --url file:///run/install/repo/liveimg.tar.gz

After fixing the error in the graphical installer, Anaconda created a separate kickstart file:
# cat anaconda-ks.cfg
#version=RHEL8
# Use live disk image installation
liveimg --url="file:///run/install/repo/liveimg.tar.gz"
# Use graphical install
graphical
....
ignoredisk --only-use=vda
# System bootloader configuration
bootloader --append="crashkernel=auto" --location=mbr --boot-drive=vda
autopart
# Partition clearing information
clearpart --none --initlabel
....
%end


I think the disk partitioning information could be included in the osbuild.ks file to fix this error

Comment 2 RHEL Program Management 2023-09-18 13:14:51 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 3 RHEL Program Management 2023-09-18 13:16:30 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.