+++ 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.
PR: https://github.com/rhinstaller/anaconda/pull/4808