Bug 57961 - DHCPRELEASE breaks dhcp failover configuration
DHCPRELEASE breaks dhcp failover configuration
Status: CLOSED WONTFIX
Product: Red Hat Linux
Classification: Retired
Component: dhcp (Show other bugs)
7.2
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Elliot Lee
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-01-03 10:36 EST by Darren Gamble
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-01-03 10:36:54 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Darren Gamble 2002-01-03 10:36:49 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)

Description of problem:
With failover, if a client issues a DHCPRELEASE, any further DHCPDISCOVERS 
by the client results in both servers responding to the request.

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


How reproducible:
Always

Steps to Reproduce:
1. Configure two DHCP servers for failover, clean out the lease files and 
activate the servers.
2. Have a client perform a DHCPRELEASE and then a DHCPDISCOVER.

	

Actual Results:  Both servers respond to the DHCPDISCOVER.

Expected Results:  Only one server should respond.

Additional info:

Redhat 7.2, installed with dhcp-3.0.1rc4-1cra.rpm .  dhcp-3.0.1 also has 
this behavior.

This problem has been posted on the dhcp-server mailing list twice, but 
there has been no response.

It doesn't appear to matter if the client obtains the lease before or 
after the servers are turned on; when the client issues the first 
DHCPRELEASE is when the problems start.

Additionally, how reliable is failover in the present version of dhcpd?  
We would like to use it for a very large number of clients, but from 
reading the mailing list I get the impression that it is not yet ready for 
production-grade service.
Comment 1 Elliot Lee 2002-01-03 11:46:50 EST
dhcp-2.0pl5 is the package in RHL 7.2 - you're using a totally custom package
that there is no chance of fixing bugs against.

The best I can do is either redirect you to the RH support/services/consulting
dudes (who will sing and dance if you pay them enough, in addition to providing
HA solutions), or tell you to keep trying with the upstream authors of dhcpd...

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