Bug 8549 - kickstart documented support of DHCP next-server does not work
Summary: kickstart documented support of DHCP next-server does not work
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: pump   
(Show other bugs)
Version: 6.1
Hardware: i386
OS: Linux
medium
high
Target Milestone: ---
Assignee: Erik Troan
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-01-17 20:14 UTC by wlf
Modified: 2008-05-01 15:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-02-14 16:48:20 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description wlf 2000-01-17 20:14:42 UTC 
According to Red Hat 6.1 Reference in Chapter 10 Kickstart Installations,
the DHCP next-server option should select the NFS server from which the
kickstart file comes. This does not work. The client always tries the DHCP
server, not the server specified on next-server. This appears to be a pump
implementation error.
Comment 1 bentlema 2000-02-09 20:17:59 UTC 
We've been using the next-server for this purposeas well, and have also noticed
that it broke in 6.1, so we had to move all of our kickstart boot files over to
the DHCP server.  Hopefully this will be fixed soon...
Comment 2 Erik Troan 2000-02-14 16:48:59 UTC 
Fixed in the piglet beta.
Note You need to log in before you can comment on or make changes to this bug.