Bug 10701

Summary:	kickstart AND no "next server" in DHCP
Product:	[Retired] Red Hat Linux	Reporter:	Derrien <derrien>
Component:	installer	Assignee:	Erik Troan <ewt>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2	CC:	derrien
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2000-04-14 19:00:35 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Derrien 2000-04-10 15:56:11 UTC

When there is no "next server" in the DHCP reply (our DHCP server Sun
Solaris seems to ignore this fields !) in kickstart installation, kickstart
tries to use 0.0.0.0 for file server.

Comment 1 Erik Troan 2000-06-16 15:20:16 UTC

What should it do instead?

Comment 2 Derrien 2000-06-16 15:33:37 UTC

From redhat-6.2/i386/doc/ref-guide/s1-kickstart2-howuse.htm :
Note that if you don't specify a server name, then the client system will
attempt to use the server that answered the BOOTP/DHCP request as its NFS server

It seems odd to try to use the server 0.0.0.0 no ?