Fix DNS connectivity issues with DVR+HA routers and DHCP-HA
Before this change, DVR_SNAT agents would get no routers when
asking for updates due to provisioning of DHCP ports on the
node they are running on. This means that there's no connectivity
between the DHCP port and the network gateway (that may be
hosted on a different node), and therefore things like DNS may
break when a VM attempts resolution when talking to the affected
DHCP port.
This change relaxed a conditional that prevents the right list of
routers to be compiled and returned from the server to the agent.
The agent on the other hand needs to make sure to allocate the
right type of router based on what is being returned from the server.
Reviewed: https:/ /review. openstack. org/522362 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=b24013f5690 24f71197370b10d d23a7647d22c73
Committed: https:/
Submitter: Zuul
Branch: master
commit b24013f569024f7 1197370b10dd23a 7647d22c73
Author: Armando Migliaccio <email address hidden>
Date: Wed Nov 22 10:59:27 2017 -0800
Fix DNS connectivity issues with DVR+HA routers and DHCP-HA
Before this change, DVR_SNAT agents would get no routers when
asking for updates due to provisioning of DHCP ports on the
node they are running on. This means that there's no connectivity
between the DHCP port and the network gateway (that may be
hosted on a different node), and therefore things like DNS may
break when a VM attempts resolution when talking to the affected
DHCP port.
This change relaxed a conditional that prevents the right list of
routers to be compiled and returned from the server to the agent.
The agent on the other hand needs to make sure to allocate the
right type of router based on what is being returned from the server.
Closes-bug: #1733987
Change-Id: I6124738c3324e0 cc3f7998e3a541f f7547f2a8a7