Bug 166933

Summary:	Obtaining hostname information has inappropriate timeout value
Product:	Red Hat Enterprise Linux 4	Reporter:	Wade Mealing <wmealing>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED DUPLICATE	QA Contact:	Mike McLean <mikem>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.0
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-08-29 18:39:53 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 Wade Mealing 2005-08-28 11:05:35 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050720 Fedora/1.0.6-1.1.fc4 Firefox/1.0.6

Description of problem:
When the machine that is being installed has a network configured, yet no DNS available, the machine will prompt you for a DNS server.  Even if this setting is left blank, anaconda still attempts to obtain dns and hostname information.  

This causes the anaconda to stall for about 3 minutes.  

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


How reproducible:
Always

Steps to Reproduce:
1. Install, have a network setup, with DHCP not handing out DNS information.
2. The installer will get a DHCP address, but no DNS information

  

Actual Results:  Server waits for about 3 minutes, the installer has not hung, although it takes excessively long to obtain an address.

Expected Results:  One would expect this to time out in a shorter time period, if your DNS is supposed to be working and it cant get an address in less than a minute, you have larger problems to deal with.

Additional info:

RHEL 4 U1.

Comment 1 Jeremy Katz 2005-08-29 18:39:53 UTC


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