Reviewed: https://review.openstack.org/522362 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=b24013f569024f71197370b10dd23a7647d22c73 Submitter: Zuul Branch: master
commit b24013f569024f71197370b10dd23a7647d22c73 Author: Armando Migliaccio <[email protected]> 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: I6124738c3324e0cc3f7998e3a541ff7547f2a8a7 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1733987 Title: name resolution error with DVR+HA routers Status in neutron: Fix Released Bug description: Steps to repro: * Deploy with multiple DHCP agents per network (e.g. 3) and multiple L3 agents per router (e.g. 2) * Create a network * Create a subnet * Create a DVR+HA router * Uplink router to external network * Deploy a VM on the network The resolv.conf of the VM looks something like this: cat /etc/resolv.conf search openstack.local nameserver 192.168.0.2 nameserver 192.168.0.4 nameserver 192.168.0.3 Where .2, .3. and .4 are your DHCP servers that relay DNS requests. Name resolution may fail when using one of these servers, due to the lack of qrouter namespace on one of the network nodes associated with the qdhcp namespace hosting the DHCP service for the network. Expected behavior: All nameservers can resolve correctly. This happens in master and prior versions. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1733987/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
