Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 140446 - driveorder value not in generated anaconda-ks.cfg
driveorder value not in generated anaconda-ks.cfg
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: anaconda (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Chris Lumens
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2004-11-22 16:54 EST by david d zuhn
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-03-09 15:21:27 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description david d zuhn 2004-11-22 16:54:41 EST
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:

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

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

Additional info:

Note You need to log in before you can comment on or make changes to this bug.