Bug 155146

Summary: failure to open anaconda generated file
Product: Red Hat Enterprise Linux 5 Reporter: Eugene Kanter <ekanter>
Component: system-config-kickstartAssignee: Chris Lumens <clumens>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5.0CC: jturner
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: RHEL4U3NAK
Fixed In Version: 5.0.0 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-06-05 17:42:41 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:
Attachments:
Description Flags
anaconda generated ks.cfg file. none

Description Eugene Kanter 2005-04-17 03:04:14 UTC 
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-17 03:04:14 UTC 
Created attachment 113276 [details]
anaconda generated ks.cfg file.
Comment 2 Chris Lumens 2005-09-08 20:56:27 UTC 
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 20:50:50 UTC 
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 17:42:41 UTC 
This will be fixed in the next major release of RHEL.