Description of problem:
Installing via a boot CD and using the kernel option "ks text" when the DHCP server has both filename and next-server correctly defined, is unable to find the kickstart file and auto install.

Version-Release number of selected component (if applicable):
dhcp-4.1.0 on RHEL5.6 and RHEL6.1 boot CD

How reproducible:
This happens every time on more than one DHCP server/client pair.

Steps to Reproduce:
1. setup a host decloration in dhcp with filename and next-server for kickstart
2. boot from the rhel6.1 CD, hit tab, enter " ks text"
3.
  
Actual results:
The install stops and a pop-up reads
"Unable to download the kickstart file.  Please modify the kickstart parameter below or press Cancel to proceed as an interactive installation."
The ctrl-alt-f3 console reads "No bootserver was found".

Expected results:
I would expect the installer to use the filename defined in DHCP as the kickstart file and to continue installing without intervention or error.



Additional info:
I reported a very similar problem with RHEL5 (Bug 448006).  Using the syntax
ks=nfs:server:/path text on the command line does work but is not preferred.