Bug 165500

Summary:	PXE boot config file for PXE install clients unusable if kickstart file has not been specified
Product:	Red Hat Enterprise Linux 4	Reporter:	Jason Vas Dias <jvdias>
Component:	system-config-netboot	Assignee:	Jason Vas Dias <jvdias>
Status:	CLOSED ERRATA	QA Contact:
Severity:	low	Docs Contact:
Priority:	medium
Version:	4.0
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	RHBA-2005-484	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-10-05 13:49:06 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	156322

Description Jason Vas Dias 2005-08-09 21:27:22 UTC

+++ 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):
system-config-netboot-0.1.20-1_EL4

How reproducible:
Always

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
  
Actual results:
The installation will fail at the point where it tries to download the kickstart
file, complaining it cannot find it.

Expected results:
The install should continue interactively.

Additional info:
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.

Comment 1 Jason Vas Dias 2005-08-09 21:35:54 UTC

This is fixed with system-config-netboot-0.1.24-1_EL4 .

Comment 7 Red Hat Bugzilla 2005-10-05 13:49:06 UTC

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.

http://rhn.redhat.com/errata/RHBA-2005-484.html