I've confirmed this bug and have determined that the problem is related to --dhcp-range not updating when the subnets are modified.
The current work around is to kill dnsmasq and then restart the dhcp agent.
I've confirmed this bug and have determined that the problem is related to --dhcp-range not updating when the subnets are modified.
The current work around is to kill dnsmasq and then restart the dhcp agent.