Bug 789719

Summary:	When the -timeout option is less than or equal to 3, dhclient will stuck in a infinite loop doing DHCP Discover
Product:	Red Hat Enterprise Linux 6	Reporter:	hydra35 <clanherb>
Component:	dhcp	Assignee:	Jiri Popelka <jpopelka>
Status:	CLOSED ERRATA	QA Contact:	Release Test Team <release-test-team>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2	CC:	ljozsa, mganisin, ovasik
Target Milestone:	rc	Keywords:	Patch
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	dhcp-4.1.1-28.P1.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-06-20 12:43:51 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description hydra35 2012-02-12 15:27:26 UTC

Description of problem:

the -timeout option specifies how many seconds will dhclient goes to background when there is no valid dhcp response.

When assigned a value less than or equal to 3 seconds, dhclient will stuck in a infinite loop doing DHCP Discover. This situation can be reproduced no matter there is valid response from server-side.


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

1. dhcp-4.1.1-25.P1_2.1(the default package comes with 6.2)
2. dhcp-4.1.1-25.P1.el6_2.1(the newest package) can be obtained via `yum update`

How reproducible: Always

Steps to Reproduce:
1. setup a dhcp server
2. run `dhclient -timeout 3 -d eth0
3. Observer the infinite loop between dhclient and dhcp server.
  
Actual results:


Expected results:


Additional info:

Comment 2 Jiri Popelka 2012-02-13 17:54:56 UTC

Thanks for the report. Problem has been in one of our patches.

Comment 6 Ladislav Jozsa 2012-04-25 12:03:23 UTC

Verified on RHEL6.3-20120416.0, dhclient-4.1.1-30.P1.el6.

Erroneous behaviour described in the opening comment is fixed.

Comment 8 errata-xmlrpc 2012-06-20 12:43:51 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0793.html