Bug 48362

Summary: anaconda flakes out prior to install
Product: [Retired] Red Hat Linux Reporter: cian cullinan <cully>
Component: anacondaAssignee: Brent Fox <bfox>
Status: CLOSED NOTABUG QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.1   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-07-10 15:29:29 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 dump file none

Description cian cullinan 2001-07-10 12:39:29 UTC 
Description of Problem:
	I'm trying to do a kickstart install on an IBM x330 server. From the cd
first of all, 	
	then over the network for the rest of them once that works. I use
mkkickstart-2.3-1, 	
	and have added in the extra part line for / as described in other bug
reports. I boot 
	from the cd, type in linux ks=floppy, anaconda starts, then dies.


How Reproducible: 100%


Steps to Reproduce:
1. mkkickstart on an identical box installed manually.
2. add root and boot partition lines to ks.cfg
3. boot from 7.1 cd, then type "linux ks=floppy at prompt"
4. anaconda starts, then dies with a trace back error

Actual Results:
	failed install

Expected Results:
	install

Additional Information:
	see attached anaconda output file
Comment 1 cian cullinan 2001-07-10 12:40:45 UTC 
Created attachment 23187 [details]
anaconda dump file
Comment 2 Brent Fox 2001-07-10 15:29:25 UTC 
I think that you don't need to do GNOME in all caps.  

If you look at the %packages section of the kickstart docs
(http://www.redhat.com/support/manuals/RHL-7.1-Manual/customization-guide/s1-kickstart2-options.html),
I think you need to say "@ Gnome Workstation" instead of "@ GNOME Workstation.
It's case sensitive.  If this doesn't fix the problem, please reopen this bug.