RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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.

I just found (Bug 653655) which would make this bug a duplicate.  Sorry I didn't find that bug report before I submitted this one.

*** This bug has been marked as a duplicate of bug 653655 ***