Bug 155146 - failure to open anaconda generated file
failure to open anaconda generated file
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: system-config-kickstart (Show other bugs)
5.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Chris Lumens
RHEL4U3NAK
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-04-16 23:04 EDT by Eugene Kanter
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version: 5.0.0
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-06-05 13:42:41 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
anaconda generated ks.cfg file. (1.46 KB, text/plain)
2005-04-16 23:04 EDT, Eugene Kanter
no flags Details

  None (edit)
Description Eugene Kanter 2005-04-16 23:04:14 EDT
Description of problem:

unable to open anaconda generated anaconda-ks.cfg

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

system-config-kickstart-2.5.16-2

How reproducible:

always

Steps to Reproduce:
1. open attached file with system-config-kickstart-2.5.16-2

  
Actual results:

traceback

Expected results:

file opens.

Additional information:

there seems to be two areas wich cause problem. they need to be taken care one
at a time. to see "--onboot no" problems comment out disk lines.

1. "--onboot no" in line 9
2. raid configuration.
Comment 1 Eugene Kanter 2005-04-16 23:04:14 EDT
Created attachment 113276 [details]
anaconda generated ks.cfg file.
Comment 2 Chris Lumens 2005-09-08 16:56:27 EDT
The same explanation on bug 163162 applies here as well, but I'm not marking
this as a duplicate of that since they're on different RHEL versions.  Adding to
proposed list.
Comment 8 Chris Lumens 2006-01-16 15:50:50 EST
There are several of these sorts of bugs in system-config-kickstart as shipped
in RHEL3, RHEL4, and their Fedora Core counterparts.  The correct fix is
essentially a reimplementation of how kickstart files are handled which is a
very invasive change with lots of potential for creating more bugs.  This work
has been done in the form of the pykickstart package for FC5.  The next major
RHEL release will pick up these changes and take care of the problem.
Comment 9 Chris Lumens 2006-06-05 13:42:41 EDT
This will be fixed in the next major release of RHEL.

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