Red Hat Bugzilla – Bug 144438
anaconda crashes when retrieving ks.cfg from CNAME nfs server
Last modified: 2007-11-30 17:07:05 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5)
Description of problem:
If kickstarting with a kickstart config file referenced via NFS to a
hostname which is actually a cname in DNS, anaconda will crash with an
un-useful error message "install exited abnormally"
Then using a syslinx config such as ...
append initrd=initrd.img-rhws-3 text load_ramdisk=1 network
Version-Release number of selected component (if applicable):
Steps to Reproduce:
set up a cname for your kickstart server in DNS, something like:
filer-cname IN CNAME real-filer-hostname
Then when booting on the system to be kickstarted enter the argument
at the boot prompt:
Actual Results: After configuring an IP address (via DHCP) and
attempts to retrieve the kickstart config file the system displays
"install exected abnormally" and then halts.
Expected Results: The system should either properly resolve the CNAME
and retrieve the kickstart config file, or display an error message
that CNAME's are not supported for retrieving kickstart configuration
Are you sure the NFS server is running on the NFS server? I do this all the
time with our internal servers without problems.
Also, what update release of RHEL 3 is this with?
Changing the 'ks=' entry to reference the IP address of the NFS server the
kickstart installation completes without error. nslookups of the CNAME resolve
the address correctly.
Red Hat Enterprise Linux WS release 3 (Taroon Update 3)
User firstname.lastname@example.org's account has been closed
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.