yahoo-eng-team team mailing list archive

[Zhixin Li <lizhixin@xxxxxxxxxxx>]

Public bug reported:

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 it
works well for most neutron services unless the metadata proxy service.
Then enable metadata-proxy true. 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 get 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:
  ** OpenStack version (Specific stable branch, or git hash if from trunk): Mitaka
  ** Linux distro, kernel. For a distro, it’s also worth knowing specific versions of client and server: all hosts are centos7
  ** DevStack or other _deployment_ mechanism? 

* Tags (Affected component): l3-agent dvr metadata-proxy

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
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:
  New

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 it
  works well for most neutron services unless the metadata proxy
  service. Then enable metadata-proxy true. 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 get 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:
    ** OpenStack version (Specific stable branch, or git hash if from trunk): Mitaka
    ** Linux distro, kernel. For a distro, it’s also worth knowing specific versions of client and server: all hosts are centos7
    ** DevStack or other _deployment_ mechanism? 

  * Tags (Affected component): l3-agent dvr metadata-proxy

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1606741/+subscriptions