Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
As an end-user of RHEL4Edge I'd like to be able to include my custom kickstart file in the (simplified-)edge-installer ISO at the build time instead of tinkering with ISOs as described here: https://access.redhat.com/solutions/60959
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
If I want to use custom kickstart file with simplified-edge-installer and edge-installer images, now I have to tinker with them as shown in the following article: https://access.redhat.com/solutions/60959 what is not really convenient.
Expected results:
I'd like to be able to specify custom kickstart file at the time of image build request, ideally as an extra parameter for compose-cli command. This would also apply for cockpit image builder.
Additional info:
Hi Rafal!
Thanks for reporting this issue. This issue is duplicated with issue https://bugzilla.redhat.com/show_bug.cgi?id=1980663. We're looking at this REF.
But simplified-installer image does not use anaconda but use coreos-installer instead. So kickstart will not work with simplified installer. Thanks!
Xiaofeng