Comment 11 for bug 1022804

I'm afraid I'm still seeing this issue on folsom. We have the lease time set to 3600 seconds, which is probably helping us trigger the issue.

I'm getting log lines of the form:
Feb 5 11:18:08 ucsprodcntl04 dnsmasq-dhcp[19754]: not using configured address 10.252.8.55 because it is leased to fa:16:3e:f6:fa:8c
Feb 5 11:18:08 ucsprodcntl04 dnsmasq-dhcp[19754]: DHCPDISCOVER(tap7a23bd1f-16) fa:16:3e:6f:72:31 no address available

Please let me know what I can do to assist.