The original bug occurred because the set of subnet cidrs changed
without a restart of dnsmasq. As a result, dnsmasq would not respond
with offers for fixed_ips assigned in the unknown cidr ranges even when
the underlying host file had properly updated.
This patch addresses the bug by restarting dnsmasq when the set of
subnet cidrs changes. When the set does not change, it will reload the
options and allocations.
Reviewed: https:/ /review. openstack. org/12397 github. com/openstack/ quantum/ commit/ 6fa761fd14f634d 4194eaa8cd64dbf c1821aac30
Committed: http://
Submitter: Jenkins
Branch: master
commit 6fa761fd14f634d 4194eaa8cd64dbf c1821aac30
Author: Mark McClain <email address hidden>
Date: Wed Sep 5 00:52:21 2012 -0400
restart dnsmasq when subnet cidr set changes
fixes bug 1045828
The original bug occurred because the set of subnet cidrs changed
without a restart of dnsmasq. As a result, dnsmasq would not respond
with offers for fixed_ips assigned in the unknown cidr ranges even when
the underlying host file had properly updated.
This patch addresses the bug by restarting dnsmasq when the set of
subnet cidrs changes. When the set does not change, it will reload the
options and allocations.
Change-Id: I0e257208750703 f4a32c51d132378 6e76e676bb6