Bug 82404 - booting from cd wtih `linux ks' doesn't get ks file from dhcp server
Summary: booting from cd wtih `linux ks' doesn't get ks file from dhcp server
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: anaconda
Version: phoebe
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
: 83149 (view as bug list)
Depends On:
Blocks: 79579
TreeView+ depends on / blocked
Reported: 2003-01-21 21:06 UTC by Alexandre Oliva
Modified: 2007-04-18 16:50 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2003-02-17 21:38:05 UTC

Attachments (Terms of Use)

Description Alexandre Oliva 2003-01-21 21:06:56 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021218

Description of problem:
Contrary to the docs in the customization guide, booting with `linux ks' doesn't
contact the dhcp server, at least when booting off the installation cd.  In VT3,
I find the message:

* grabbing kickstart from nfs with dhcp next-server currently unsupported

but this is certainly a glitch, since I have only one dhcp server active in this
network, and it definitely doesn't have the next-server option set.  Besides, it
was not contacted at all from the boot to the appearance of the message.

Adding `askmethod' to the boot line doesn't help.  Trying at random `ks=nfs'
changes the message to `reading kickstart file', regardless of the presence of
askmethod or not, but it just hangs there, without having ever contacted the
dhcp server.

`ks=nfs:' works as far as setting up networking goes, but it doesn't grab
information from dhcp as I had hoped it might.  `ks=dhcp:' (desperate try! :-)
hangs just like `ks=nfs' .

The solution was to boot `linux ks=nfs:server:/pathname', which is sub-optimal.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Use a dhcp server that had been used for kickstart installs of up to RHL7.3
2.boot off the cd with linux ks


Actual Results:  it doesn't bring up the network interface to obtain dhcp ks

Expected Results:  according to the docs, it should

Additional info:

Comment 3 Jeremy Katz 2003-01-23 22:25:05 UTC
It's back in CVS

Comment 4 Jeremy Katz 2003-01-30 19:55:59 UTC
*** Bug 83149 has been marked as a duplicate of this bug. ***

Comment 5 Alexandre Oliva 2003-02-17 21:38:05 UTC
Confirmed fixed in current tree.

Note You need to log in before you can comment on or make changes to this bug.