Bug 79386

Summary:	kickstart ondisk fails if specified drive missing
Product:	[Retired] Red Hat Linux	Reporter:	Bill Heiden <bill.heiden>
Component:	anaconda	Assignee:	Jeremy Katz <katzj>
Status:	CLOSED RAWHIDE	QA Contact:	Mike McLean <mikem>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.2	Keywords:	FutureFeature
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2003-07-28 23:17:30 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:

Description Bill Heiden 2002-12-11 02:51:08 UTC

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 4.0)

Description of problem:
 Within our facility, we are using a general ks.cfg to install machines.  This 
general ks.cfg uses ondisk within the partition section to create filesystems.  
We create /boot, swap, and / on the primary drive (/dev/sda) and then create 
a /vol2 on /dev/sdb.  If the machine does not have a /dev/sdb, then the 
kickstart installation aborts. It would be great if the installation continued 
and posted a message to one of the log files informing us of the error.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Obtain machine with only a single drive
2. Create a ks.cfg that attempts to create a partition/filesystem on a 
secondary non-existent drive.
3. Install using the ks.cfg from step and watch the failure.
	

Additional info:

Comment 1 Brent Fox 2002-12-11 04:28:53 UTC

Changing component to anaconda since this seems related to kickstart and not the
kickstart configuration tool.

Comment 2 Jeremy Katz 2003-01-10 06:52:39 UTC

Will address as time allows -- in general, kickstart assumes that your kickstart
config is appropriate for the machine being installed on.

Comment 3 Jeremy Katz 2003-07-09 05:02:54 UTC

We give a slightly better exception now.  Still need to catch and provide
user-friendly error messages some day, though.