Partner-Down question on version 3.1.0

[Jack Kielsmeier]

Hello,

I am testing different scenarios with DHCP failover before I put a
couple of failover servers into production.

The scenario I tested today:

I put one DHCP server into the partner down state:

Nov  5 10:50:38 dhcp-dsm dhcpd: [ID 702911 local5.info] failover peer dhcp-failover: I move from partner-down to startup
Nov  5 10:50:52 dhcp-dsm dhcpd: [ID 702911 local5.info] failover peer dhcp-failover: I move from startup to partner-down

Even in partner down state, I see log messages such as the following:

Nov  5 10:55:24 dhcp-dsm dhcpd: [ID 702911 local5.debug] DHCPREQUEST for 67.55.194.44 from 00:15:f2:94:59:ff via 67.55.194.254: lease owned by peer
Nov  5 10:55:27 dhcp-dsm dhcpd: [ID 702911 local5.debug] DHCPREQUEST for 67.55.194.45 from 00:1e:2a:69:52:bd via 67.55.194.254: lease owned by peer

Shouldn't the server in the "partner-down" state be able to renew any
valid lease?

It should be stated when I did this test that the redundant dhcp servers
had no lease information for this subnet (Basically, this subnet's
traffic was moved from a production, non-redundant DHCP server). Clients
had an active lease from the OLD dhcp server and were trying to renew
their leases to the test DHCP server I put into the partner-down state.

Many leases did get renewed, only some of them ran into the "lease owned by peer"
issue. Is this some sort of bug?

Thank you,

-- 
Jack Kielsmeier <jackkiel at netins.net>