Bug 27493

Summary: anaconda crashes when attempting kickstart via nfs
Product: [Retired] Red Hat Linux Reporter: Philip J. Hollenback <philiph>
Component: anacondaAssignee: Michael Fulbright <msf>
Status: CLOSED NOTABUG QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2   
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-02-27 23:53:15 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
sample kickstart config file none

Description Philip J. Hollenback 2001-02-14 03:37:39 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.2.18 i686)


When I try to start a kickstart install off the rh62 install cd with 'linux
ks' at the lilo prompt, anaconda dies with a stack trace indicating
"--kickstart: missing argument"

Reproducible: Always
Steps to Reproduce:
1.boot rh62 install cd
2.type 'linux ks' at the lilo prompt
3.anaconda dies
	

Actual Results:  A stack trace along these lines:

file "/usr/bin/anaconda" line 45 in ? [ "gui" "text" ... ]
file /usr/lib/anaconda/isys.py line 198 in getopt
return apply (_iss.getopt.args)
TypeError: bad argument --kickstart: missing argument

Expected Results:  system starts a kickstart install, queries my dhcp
server for an address, and retrieves the kickstart config file from my nfs
server.

I've verified with a network sniffer that the install doesn't get as far as
requesting a dhcp address or making an nfs mount.

It seems like anaconda expects something after 'ks' on the kernel load
line, but the docs indicate that 'ks' is sufficient.

I've also tried an explicit kickstart via nfs with the lilo line

'linux ks=nfs:10.1.3.2:/kickstart/ks.cfg'

which causes the installer to not do a kickstart install at all, and
instead do a manual install.
Comment 1 Michael Fulbright 2001-02-14 17:44:48 UTC 
Brock do you recall any 6.2 related ks issues with NFS?
Comment 2 Brock Organ 2001-02-14 22:16:22 UTC 
could you supply the kickstart file that fails for you?  We'll try to reproduce
the problem here in our test lab ...
Comment 3 Philip J. Hollenback 2001-02-15 00:47:56 UTC 
Created attachment 10060 [details]
sample kickstart config file
Comment 4 Philip J. Hollenback 2001-02-15 00:50:07 UTC 
I've atached the kickstart config file I'm using, but note that this file never
gets read - anaconda dies before it gets a dhcp address or mounts the nfs
directory where this file resides.

I've tried kickstarting by placing this file on an existing hd partition, and it
does work that way.
Comment 5 Michael Fulbright 2001-02-27 23:53:11 UTC 
When you try the NFS ks and it fails, look on VC3 (cntl-alt-f3) for any nfs/ks
related messages and let us know what they say.
Comment 6 Michael Fulbright 2001-04-02 20:00:38 UTC 
Closing due to inactivity - please reopen if you have anything to add to the bug
report.