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.
+++ This bug was initially created as a clone of Bug #2077045 +++
Description of problem:
The installer prints an error when running a kickstart installation with the kickstart file on disk. Despite the error message, the kickstart file is successfully used for the installation, so it's not a blocking issue:
############## Installer errors encountered during boot ##############
unknown network kickstart URL: hd:disk/by-uuid/4bea3f40-e8f7-4990-be75-06f0cfd3ebf2:/192.168.122.236-1650464282
Version-Release number of selected component (if applicable):
RHEL-9.0
anaconda-34.25.0.29-1.el9_0
How reproducible:
Always
Steps to Reproduce:
1. Prepare a kickstart file on a disk partition.
2. Use the kickstart file during the installation (inst.ks=hd:disk/by-uuid/<UUID>:/<FILENAME>).
Actual results:
An error on the console. The kickstart file is successfully used.
Expected results:
No errors related to kickstart.
Additional info:
The error is displayed also in case of "inst.ks=cdrom:/ks.cfg" on the kernel cmdline (see bug 2178281):
"unknown network kickstart URL: cdrom:/ks.cfg"
This is clone of RHEL-9 bug. The issue is also on RHEL-8 bug because we don't have here print of the booting issues in stage2 the error could be saw only in the journal log.
To test this check the journal for the above message.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (anaconda bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2023:6957