Red Hat Bugzilla – Bug 165500
PXE boot config file for PXE install clients unusable if kickstart file has not been specified
Last modified: 2007-11-30 17:07:19 EST
+++ This bug was initially created as a clone of Bug #164776 +++
Description of problem:
If you configure a client for 'Network OS install' and leave the 'Kickstart
File' field empty, the installation of the client will fail because it cannot
find a kickstart file named "".
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. start redhat-config-netboot
2. configure a Network Installation profile
3. configure a client with this profile and leave the 'kickstart file' field empty.
4. boot the client
The installation will fail at the point where it tries to download the kickstart
file, complaining it cannot find it.
The install should continue interactively.
Doing kickstart-less network installs may sound unusual, but it is very
convenient for systems where you cannot boot from CD/DVD.
In redhat-config-netboot the problem can be solved easily by checking whether a
kickstart file has been specified and ommitting the 'ks=' parameter if it hasn't.
But maybe the proper solution would be if the installer compononent (anaconda?)
would interpret an empty ks parameter as equivalent to no kickstart file at all.
This is fixed with system-config-netboot-0.1.24-1_EL4 .
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.