From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 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 ... default ks label ks kernel vmlinuz-rhws-3 append initrd=initrd.img-rhws-3 text load_ramdisk=1 network ks=nfs:a-cname:/kickstarts/generic-rhws3-ks.cfg ... Version-Release number of selected component (if applicable): How reproducible: Always 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: linux ks=nfs:filer-cname:/kickstarts/generic-rhws3-ks.cfg 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 files. Additional info:
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. from /etc/redhat-release Red Hat Enterprise Linux WS release 3 (Taroon Update 3)
User pnasrat'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: http://www.redhat.com/security/updates/errata/ 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.