Bug 5589 - 6.1 kickstart doesn't look at BOOTP/DHCP next-server
6.1 kickstart doesn't look at BOOTP/DHCP next-server
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Erik Troan
Depends On:
  Show dependency treegraph
Reported: 1999-10-05 12:00 EDT by ilh
Modified: 2008-05-01 11:37 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-02-03 10:51:07 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description ilh 1999-10-05 12:00:11 EDT
I have been successfully using kickstart with 5.2 and 6.0.
On my BOOTP/DHCP server, I specify next-server and a
kickstart filename on that server.  Note that next-server is
different from the BOOTP/DHCP server.

In 6.1, the installer doesn't seem to pay attention to
next-server, but instead tries to NFS mount the kickstart
config file from the BOOTP/DHCP server.  Of course this

Is this intentional?  Is there a workaround?

As it stands, it looks like I'll have to put the kickstart
config on the floppy, and I'd rather not do this if I can
help it.
Comment 1 ilh 1999-10-05 12:34:59 EDT
It appears to me the change to pump caused the problem.  It appears
that pump ignores the next-server specification.  Ugh.
Comment 2 ilh 1999-10-05 12:42:59 EDT
It appears to me the change to pump caused the problem.  It appears
that pump ignores the next-server specification.  Ugh.

------- Additional Comments From   10/18/99 10:57 -------
I see this on my end as well.  Very frustrating.
Comment 3 Jay Turner 1999-10-20 15:11:59 EDT
This issue has been forwarded to a developer for further action.
Comment 4 Jay Turner 1999-10-22 10:05:59 EDT
*** Bug 6202 has been marked as a duplicate of this bug. ***

When attempting a kickstart/DHCP/NFS install, the installer
attempts to mount the DHCP server instead of the machine
defined by the next-server in the dhcpd.conf:

The following dhcpd.conf stanza worked w/ RH6.0, but now
fails with the message "failed to mount" on the Alt+F3 console:

 group {
        filename "/root/kickstart/wyrd.node";

        host forte2 {
                hardware ethernet 00:a0:cc:56:1c:4a;
    } is the IP address of the dhcpd server.

------- Additional Comments From   10/31/99 22:11 -------

Adding the non-obvious

  option dhcp-server-identifier;

to your ISC dhcpd.conf will enable you to kickstart (at least it seams

Love <lha@stacken.kth.se>
Comment 5 Karl Burkett 2000-01-18 14:13:59 EST
Just discovered this problem myself.  I'll be trying to NFS mount the directory
that contains all of the config files back to the DHCP server.  Ugly - with out
a doubt - but if I keep the paths the same it won't break when RH gets the
next-server call functioning at some point.
Comment 6 Karl Burkett 2000-01-18 15:23:59 EST
Well that was a dumb idea - can't share and nfs mounted file system.  Back to
the drawing board again.
Comment 7 panu.matilainen 2000-01-25 08:17:59 EST
Just noticed that this is fixed in the Rawhide bootnet.img.
Comment 8 Erik Troan 2000-02-03 10:51:59 EST
This is fixed for the next release (and current rawhide)

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