Comment 15 for bug 1457404

Today's update: we haven't managed to reproduce this locally yet. Just looking at logs it doesn't seem to be vmware specific, but it *may* have something to do with FlatDHCPManager vs VlanManager differences. It's easy to trigger this synthetically though, by `forgetting` to fire DHCPRELEASE. But it's still unclear how dnsmasq misses it on a real environment (sending SIGHUPs to dnsmasq in a loop didn't make it miss a single DHCPRELEASE sent on a test env). The workaround would be to send a few DHCPRELEASE packets or do that after a short sleep. Although, I'd like us to get a stable repro, before we actually try to do that.

Overall, this condition seems to be rather hard to trigger. IMO, it shouldn't be a blocker for us in 6.1. Still, on request from PI team we continue to track this as a high priority bug.