DHCPRELEASE question

[Darren]

I have seen some strange behavior that I do not understand.  I have a failover setup with version 3.1.3.  Lease length as reported by the client is 43,200 seconds.  I can do a discover and get an address:

Apr 15 19:30:23 server-1 dhcpd: DHCPDISCOVER from 00:50:bf:d3:2a:d4 via 74.115.183.241
Apr 15 19:30:23 server-1 dhcpd: DHCPOFFER on 74.115.183.254 to 00:50:bf:d3:2a:d4 via 74.115.183.241
Apr 15 19:30:23 server-1 dhcpd: DHCPREQUEST for 74.115.183.254 (74.115.183.234) from 00:50:bf:d3:2a:d4 via 74.115.183.241
Apr 15 19:30:23 server-1 dhcpd: DHCPACK on 74.115.183.254 to 00:50:bf:d3:2a:d4 via 74.115.183.241
.....
Apr 15 19:30:23 server-2 dhcpd: DHCPDISCOVER from 00:50:bf:d3:2a:d4 via 74.115.183.241
Apr 15 19:30:23 server-2 dhcpd: DHCPOFFER on 74.115.183.254 to 00:50:bf:d3:2a:d4 via 74.115.183.241
Apr 15 19:30:23 server-2 dhcpd: DHCPREQUEST for 74.115.183.254 (74.115.183.234) from 00:50:bf:d3:2a:d4 via 74.115.183.241
Apr 15 19:30:23 server-2 dhcpd: DHCPACK on 74.115.183.254 to 00:50:bf:d3:2a:d4 via 74.115.183.241

Then I do a release:

Apr 15 19:30:29 server-2 dhcpd: DHCPRELEASE of 74.115.183.254 from 00:50:bf:d3:2a:d4 via eth0 (not found)


As you can see, this release happened only six seconds later, why was the lease "not found"?

Server:

Linux 2.6.26.8
isc dhcpd 3.1.3

Client:
xubuntu 8.10
isc dhcp (client) 3.1.2

For giggles, I did it again and let more time pass before doing the release:

Apr 15 19:34:32 server-1 dhcpd: DHCPDISCOVER from 00:50:bf:d3:2a:d4 via 74.115.183.241
Apr 15 19:34:32 server-1 dhcpd: DHCPOFFER on 74.115.183.254 to 00:50:bf:d3:2a:d4 via 74.115.183.241
Apr 15 19:34:32 server-1 dhcpd: DHCPREQUEST for 74.115.183.254 (74.115.183.234) from 00:50:bf:d3:2a:d4 via 74.115.183.241
Apr 15 19:34:32 server-1 dhcpd: DHCPACK on 74.115.183.254 to 00:50:bf:d3:2a:d4 via 74.115.183.241
Apr 15 19:35:04 server-1 dhcpd: DHCPREQUEST for 74.115.183.254 from 00:50:bf:d3:2a:d4 via 74.115.183.241
Apr 15 19:35:04 server-1 dhcpd: DHCPACK on 74.115.183.254 to 00:50:bf:d3:2a:d4 via 74.115.183.241
Apr 15 19:36:25 server-1 dhcpd: DHCPRELEASE of 74.115.183.254 from 00:50:bf:d3:2a:d4 via eth0 (not found)
.....
Apr 15 19:34:32 server-2 dhcpd: DHCPDISCOVER from 00:50:bf:d3:2a:d4 via 74.115.183.241
Apr 15 19:34:32 server-2 dhcpd: DHCPOFFER on 74.115.183.254 to 00:50:bf:d3:2a:d4 via 74.115.183.241
Apr 15 19:34:32 server-2 dhcpd: DHCPREQUEST for 74.115.183.254 (74.115.183.234) from 00:50:bf:d3:2a:d4 via 74.115.183.241
Apr 15 19:34:32 server-2 dhcpd: DHCPACK on 74.115.183.254 to 00:50:bf:d3:2a:d4 via 74.115.183.241
Apr 15 19:35:04 server-2 dhcpd: DHCPREQUEST for 74.115.183.254 from 00:50:bf:d3:2a:d4 via 74.115.183.241
Apr 15 19:35:04 server-2 dhcpd: DHCPACK on 74.115.183.254 to 00:50:bf:d3:2a:d4 via 74.115.183.241

The difference I see here is that the release ended up on server-1 instead of server-2.  It still wasn't "found", however.

Since the release does not "find" the lease, no event is generated which is causing some problems in some other areas.

Any idea what the deal is?  Is this fixed in the 4.x.x tree?