Reviewed: https://review.openstack.org/639979 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=6ae228cc2e75504d9a8f35e3480a66707f9d7246 Submitter: Zuul Branch: master
commit 6ae228cc2e75504d9a8f35e3480a66707f9d7246 Author: Slawek Kaplonski <[email protected]> Date: Thu Feb 28 11:35:07 2019 +0100 Spawn metadata proxy on dvr ha standby routers In case when L3 agent is running in dvr_snat mode on compute node, it is like that e.g. in some of the gate jobs, it may happen that same router is scheduled to be in standby mode on compute node and on same compute node there is instance connected to it. So in such case metadata proxy needs to be spawned in router namespace even if it is in standby mode. Change-Id: Id646ab2c184c7a1d5ac38286a0162dd37d72df6e Closes-Bug: #1817956 Closes-Bug: #1606741 ** 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/1606741 Title: Metadata service for instances is unavailable when the l3-agent on the compute host is dvr_snat mode Status in neutron: Fix Released Bug description: In my mitaka environment, there are five nodes here, including controller, network1, network2, computer1, computer2 node. I start l3-agents with dvr_snat mode in all network and compute nodes and set enable_metadata_proxy to true in l3-agent.ini. It works well for most neutron services unless the metadata proxy service. When I run command "curl http://169.254.169.254"; in an instance booting from cirros, it returns "curl: couldn't connect to host" and the instance can't fetch metadata in its first booting. * Pre-conditions: start l3-agent with dvr_snat mode in all computer and network nodes and set enable_metadata_proxy to true in l3-agent.ini. * Step-by-step reproduction steps: 1.create a network and a subnet under this network; 2.create a router; 3.add the subnet to the router 4.create an instance with cirros (or other images) on this subnet 5.open the console for this instance and run command 'curl http://169.254.169.254' in bash, waiting for result. * Expected output: this command should return the true metadata info with the command 'curl http://169.254.169.254' * Actual output: the command actually returns "curl: couldn't connect to host" * Version: ** Mitaka ** All hosts are centos7 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1606741/+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
