This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2128798 - When building a RHEL ISO, "Kickstart is insufficient"
Summary: When building a RHEL ISO, "Kickstart is insufficient"
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: osbuild-composer
Version: 8.6
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Image Builder team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-21 14:10 UTC by Christophe Besson
Modified: 2023-09-18 13:20 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-18 13:16:30 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-4604 0 None Migrated None 2023-09-18 13:16:24 UTC
Red Hat Issue Tracker RHELPLAN-134588 0 None None None 2022-09-21 14:16:27 UTC
Red Hat Knowledge Base (Solution) 6977658 0 None None None 2022-09-27 10:47:29 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.