Bug 140446

Summary:	driveorder value not in generated anaconda-ks.cfg
Product:	Red Hat Enterprise Linux 3	Reporter:	david d zuhn <zoo>
Component:	anaconda	Assignee:	Chris Lumens <clumens>
Status:	CLOSED RAWHIDE	QA Contact:	Mike McLean <mikem>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.0	CC:	nobody+pnasrat
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:	FC4
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-03-09 20:21:27 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 david d zuhn 2004-11-22 21:54:41 UTC

Description of problem:

I have a system with several HBAs installed, which show up as sda
through sdc, with my local SCSI drive (which should be the boot disk)
as sde.  

I need to change the driveorder value during the installation (using
the Advanced Boot Loader Options screen).    However, the generated
kickstart file (installed as /root/anaconda-ks.cfg) doesn't reflect
this setting.

This bug is representive of a larger problem -- I have hopes that a
manual installation of a system, using whatever options and choices
made by the user, can be completely recreated by a kickstart file, and
that the generated kickstart file should reflect EVERY choice and
setting made by the user.


Version-Release number of selected component (if applicable):
RHEL 3AS (Update 3)  anaconda 9.1.3-3.RHEL

How reproducible:
completely.

Steps to Reproduce:
1. perform an installation, changing the driveorder
2. boot the system, examine /root/anaconda-ks.cfg
3.
  
Actual results:
no driveorder option

Expected results:
the option value as selected by the user should be present

Additional info: