Red Hat Bugzilla – Bug 84459
Dont have installer crash if kickstart NFS mount fails
Last modified: 2007-04-18 12:51:19 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030120
Description of problem:
After assuming that a kickstart file I had created by hand had something broken
that caused the installer to crash, I did a non-kickstart install, took the
generated kickstart file (attached) and put it up in the server that serves
kickstart files. The installer crashed just the same, right after reading the
kickstart file in.
I booted with `linux ks', and vt4 shows it going its IP infromation from the
DHCP server, while vt3 displays the correct location of the ks file. that's the
last thing in vt3.
vt1 says `install exited abnormally -- received signal 11', and then a shutdown
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Put this ks file up on an NFS server
2.Boot with `linux ks' (or use the explicit nfs syntax, it doesn't make any
Actual Results: The installer crashes
Expected Results: If there's something wrong with the kickstart file, it should
tell me so. But I don't think that's it.
Created attachment 90137 [details]
anaconda-generated kickstart file, except for [omitted] instead of root and grub passwords
Adding an install source line to this config doesn't cause a crash for me. Your
encrypted password doesn't happen to contain something that would get mishandled
by popt does it?
Problem was that the kickstart NFS server wasn't running nfsd. Doh!
Still, the error message doesn't quite help one figure out what the problem is :-(