2016-07-27 01:29:22 |
Zhixin Li |
bug |
|
|
added bug |
2016-07-27 02:29:19 |
Zhixin Li |
tags |
|
l3-dvr-backlog |
|
2016-07-27 02:29:32 |
Zhixin Li |
tags |
l3-dvr-backlog |
l3-bgp l3-dvr-backlog |
|
2016-07-27 02:29:51 |
Zhixin Li |
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 |
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? |
|
2016-07-27 02:30:49 |
Zhixin Li |
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? |
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:
** Mitaka
** All hosts are centos7 |
|
2016-07-27 03:10:06 |
Zhixin Li |
neutron: assignee |
|
Zhixin Li (lizhixin) |
|
2016-07-27 03:12:41 |
Zhixin Li |
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:
** Mitaka
** All hosts are centos7 |
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 |
|
2016-07-27 03:45:52 |
Zhixin Li |
tags |
l3-bgp l3-dvr-backlog |
l3-dvr-backlog l3-ha |
|
2016-07-27 09:18:44 |
Jakub Libosvar |
neutron: importance |
Undecided |
High |
|
2016-07-27 15:09:55 |
Brian Haley |
bug |
|
|
added subscriber Brian Haley |
2016-07-28 00:57:14 |
Dongcan Ye |
bug |
|
|
added subscriber Dongcan Ye |
2016-09-01 09:01:36 |
OpenStack Infra |
neutron: status |
New |
In Progress |
|
2016-09-01 09:01:36 |
OpenStack Infra |
neutron: assignee |
Zhixin Li (lizhixin) |
Dongcan Ye (hellochosen) |
|
2016-09-02 19:56:27 |
OpenStack Infra |
neutron: assignee |
Dongcan Ye (hellochosen) |
Brian Haley (brian-haley) |
|
2016-09-22 10:55:48 |
OpenStack Infra |
neutron: assignee |
Brian Haley (brian-haley) |
Zhixin Li (lizhixin) |
|
2016-09-30 02:45:34 |
Zhixin Li |
neutron: assignee |
Zhixin Li (lizhixin) |
|
|
2016-11-23 15:09:12 |
Brian Haley |
neutron: importance |
High |
Medium |
|
2018-01-10 17:32:43 |
Ivan Borisov |
bug |
|
|
added subscriber Ivan Borisov |
2018-10-26 23:17:05 |
Swaminathan Vasudevan |
neutron: status |
In Progress |
Confirmed |
|
2018-10-26 23:17:26 |
Swaminathan Vasudevan |
neutron: status |
Confirmed |
Won't Fix |
|
2019-03-01 19:54:07 |
OpenStack Infra |
neutron: status |
Won't Fix |
In Progress |
|
2019-03-01 19:54:07 |
OpenStack Infra |
neutron: assignee |
|
Slawek Kaplonski (slaweq) |
|
2019-03-08 00:24:45 |
OpenStack Infra |
neutron: status |
In Progress |
Fix Released |
|
2019-03-12 12:30:46 |
OpenStack Infra |
tags |
l3-dvr-backlog l3-ha |
in-stable-queens l3-dvr-backlog l3-ha |
|
2019-03-12 23:46:05 |
OpenStack Infra |
tags |
in-stable-queens l3-dvr-backlog l3-ha |
in-stable-queens in-stable-rocky l3-dvr-backlog l3-ha |
|
2019-03-17 17:55:16 |
OpenStack Infra |
tags |
in-stable-queens in-stable-rocky l3-dvr-backlog l3-ha |
in-stable-pike in-stable-queens in-stable-rocky l3-dvr-backlog l3-ha |
|
2019-05-10 16:07:51 |
Edward Hope-Morley |
bug task added |
|
cloud-archive |
|
2019-05-10 16:08:30 |
Edward Hope-Morley |
nominated for series |
|
cloud-archive/stein |
|
2019-05-10 16:08:30 |
Edward Hope-Morley |
bug task added |
|
cloud-archive/stein |
|
2019-05-10 16:08:30 |
Edward Hope-Morley |
nominated for series |
|
cloud-archive/queens |
|
2019-05-10 16:08:30 |
Edward Hope-Morley |
bug task added |
|
cloud-archive/queens |
|
2019-05-10 16:08:30 |
Edward Hope-Morley |
nominated for series |
|
cloud-archive/rocky |
|
2019-05-10 16:08:30 |
Edward Hope-Morley |
bug task added |
|
cloud-archive/rocky |
|
2019-05-10 16:09:05 |
Corey Bryant |
bug task added |
|
neutron (Ubuntu) |
|
2019-05-10 16:10:55 |
Edward Hope-Morley |
cloud-archive/stein: status |
New |
Fix Released |
|
2019-05-10 16:15:43 |
Edward Hope-Morley |
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 |
[Impact]
Currently if you deploy Openstack with dvr and l3ha enabled (and > 1 compute host) only instances that are booted on the compute host that is running the VR master will have access to metadata. This patch ensures that both master and slave VRs have an associated haproxy ns-metadata proccess running local to the compute host.
[Test Case]
* deploy Openstack with dvr and l3ha enabled with 2 compute hosts
* create an ubuntu instance on each compute hosts
* check that both are able to access the metadata api (i.e. cloud-init completes successfully)
* verify that there is an ns-metadata haproxy process running on each compute host
[Regression Potential]
None anticipated
=============================================================================
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 |
|
2019-05-10 16:15:54 |
Dmitrii Shcherbakov |
bug |
|
|
added subscriber Dmitrii Shcherbakov |
2019-05-10 16:15:58 |
Edward Hope-Morley |
tags |
in-stable-pike in-stable-queens in-stable-rocky l3-dvr-backlog l3-ha |
in-stable-pike in-stable-queens in-stable-rocky l3-dvr-backlog l3-ha sts-sru-needed |
|
2019-05-10 16:16:10 |
Edward Hope-Morley |
summary |
Metadata service for instances is unavailable when the l3-agent on the compute host is dvr_snat mode |
[SRU] Metadata service for instances is unavailable when the l3-agent on the compute host is dvr_snat mode |
|
2019-05-10 16:28:14 |
Edward Hope-Morley |
attachment added |
|
lp1606741-rocky.debdiff https://bugs.launchpad.net/cloud-archive/+bug/1606741/+attachment/5262965/+files/lp1606741-rocky.debdiff |
|
2019-05-10 16:28:50 |
Corey Bryant |
nominated for series |
|
Ubuntu Bionic |
|
2019-05-10 16:28:50 |
Corey Bryant |
bug task added |
|
neutron (Ubuntu Bionic) |
|
2019-05-10 16:28:50 |
Corey Bryant |
nominated for series |
|
Ubuntu Disco |
|
2019-05-10 16:28:50 |
Corey Bryant |
bug task added |
|
neutron (Ubuntu Disco) |
|
2019-05-10 16:28:50 |
Corey Bryant |
nominated for series |
|
Ubuntu Eoan |
|
2019-05-10 16:28:50 |
Corey Bryant |
bug task added |
|
neutron (Ubuntu Eoan) |
|
2019-05-10 16:28:50 |
Corey Bryant |
nominated for series |
|
Ubuntu Cosmic |
|
2019-05-10 16:28:50 |
Corey Bryant |
bug task added |
|
neutron (Ubuntu Cosmic) |
|
2019-05-10 16:29:09 |
Corey Bryant |
neutron (Ubuntu Eoan): importance |
Undecided |
High |
|
2019-05-10 16:29:09 |
Corey Bryant |
neutron (Ubuntu Eoan): status |
New |
Fix Released |
|
2019-05-10 16:30:04 |
Corey Bryant |
neutron (Ubuntu Disco): importance |
Undecided |
High |
|
2019-05-10 16:30:04 |
Corey Bryant |
neutron (Ubuntu Disco): status |
New |
Fix Released |
|
2019-05-10 16:30:36 |
Corey Bryant |
neutron (Ubuntu Cosmic): importance |
Undecided |
High |
|
2019-05-10 16:30:36 |
Corey Bryant |
neutron (Ubuntu Cosmic): status |
New |
Triaged |
|
2019-05-10 16:31:17 |
Corey Bryant |
neutron (Ubuntu Bionic): importance |
Undecided |
High |
|
2019-05-10 16:31:17 |
Corey Bryant |
neutron (Ubuntu Bionic): status |
New |
Triaged |
|
2019-05-10 16:34:29 |
Corey Bryant |
cloud-archive/rocky: importance |
Undecided |
High |
|
2019-05-10 16:34:29 |
Corey Bryant |
cloud-archive/rocky: status |
New |
Triaged |
|
2019-05-10 16:34:42 |
Corey Bryant |
cloud-archive/queens: importance |
Undecided |
High |
|
2019-05-10 16:34:42 |
Corey Bryant |
cloud-archive/queens: status |
New |
Triaged |
|
2019-05-10 18:20:10 |
Corey Bryant |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
2019-05-10 18:25:54 |
Steve Langasek |
neutron (Ubuntu Cosmic): status |
Triaged |
Fix Committed |
|
2019-05-10 18:26:00 |
Steve Langasek |
bug |
|
|
added subscriber SRU Verification |
2019-05-10 18:26:05 |
Steve Langasek |
tags |
in-stable-pike in-stable-queens in-stable-rocky l3-dvr-backlog l3-ha sts-sru-needed |
in-stable-pike in-stable-queens in-stable-rocky l3-dvr-backlog l3-ha sts-sru-needed verification-needed verification-needed-cosmic |
|
2019-05-13 09:06:14 |
Edward Hope-Morley |
tags |
in-stable-pike in-stable-queens in-stable-rocky l3-dvr-backlog l3-ha sts-sru-needed verification-needed verification-needed-cosmic |
in-stable-pike in-stable-queens in-stable-rocky l3-dvr-backlog l3-ha sts-sru-needed verification-done verification-done-cosmic |
|
2019-05-13 13:34:04 |
Corey Bryant |
cloud-archive/rocky: status |
Triaged |
Fix Committed |
|
2019-05-13 13:34:07 |
Corey Bryant |
tags |
in-stable-pike in-stable-queens in-stable-rocky l3-dvr-backlog l3-ha sts-sru-needed verification-done verification-done-cosmic |
in-stable-pike in-stable-queens in-stable-rocky l3-dvr-backlog l3-ha sts-sru-needed verification-done verification-done-cosmic verification-rocky-needed |
|
2019-05-15 14:47:51 |
Edward Hope-Morley |
tags |
in-stable-pike in-stable-queens in-stable-rocky l3-dvr-backlog l3-ha sts-sru-needed verification-done verification-done-cosmic verification-rocky-needed |
in-stable-pike in-stable-queens in-stable-rocky l3-dvr-backlog l3-ha sts-sru-needed verification-done verification-done-cosmic verification-rocky-done |
|
2019-05-20 08:39:37 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
2019-05-20 08:41:21 |
Łukasz Zemczak |
neutron (Ubuntu Bionic): status |
Triaged |
Fix Committed |
|
2019-05-20 08:41:24 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
2019-05-20 08:41:29 |
Łukasz Zemczak |
tags |
in-stable-pike in-stable-queens in-stable-rocky l3-dvr-backlog l3-ha sts-sru-needed verification-done verification-done-cosmic verification-rocky-done |
in-stable-pike in-stable-queens in-stable-rocky l3-dvr-backlog l3-ha sts-sru-needed verification-done-cosmic verification-needed verification-needed-bionic verification-rocky-done |
|
2019-05-20 08:49:40 |
Launchpad Janitor |
neutron (Ubuntu Cosmic): status |
Fix Committed |
Fix Released |
|
2019-05-20 11:59:57 |
Corey Bryant |
cloud-archive/rocky: status |
Fix Committed |
Fix Released |
|
2019-05-20 17:14:32 |
Corey Bryant |
cloud-archive/queens: status |
Triaged |
Fix Committed |
|
2019-05-20 17:14:35 |
Corey Bryant |
tags |
in-stable-pike in-stable-queens in-stable-rocky l3-dvr-backlog l3-ha sts-sru-needed verification-done-cosmic verification-needed verification-needed-bionic verification-rocky-done |
in-stable-pike in-stable-queens in-stable-rocky l3-dvr-backlog l3-ha sts-sru-needed verification-done-cosmic verification-needed verification-needed-bionic verification-queens-needed verification-rocky-done |
|
2019-05-23 18:51:07 |
Edward Hope-Morley |
tags |
in-stable-pike in-stable-queens in-stable-rocky l3-dvr-backlog l3-ha sts-sru-needed verification-done-cosmic verification-needed verification-needed-bionic verification-queens-needed verification-rocky-done |
in-stable-pike in-stable-queens in-stable-rocky l3-dvr-backlog l3-ha sts-sru-needed verification-done-bionic verification-done-cosmic verification-needed verification-queens-needed verification-rocky-done |
|
2019-05-27 12:08:29 |
Launchpad Janitor |
neutron (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
2019-05-29 08:53:37 |
Edward Hope-Morley |
tags |
in-stable-pike in-stable-queens in-stable-rocky l3-dvr-backlog l3-ha sts-sru-needed verification-done-bionic verification-done-cosmic verification-needed verification-queens-needed verification-rocky-done |
in-stable-pike in-stable-queens in-stable-rocky l3-dvr-backlog l3-ha sts-sru-done verification-done verification-done-bionic verification-done-cosmic verification-queens-done verification-rocky-done |
|
2019-05-29 11:07:52 |
Corey Bryant |
cloud-archive/queens: status |
Fix Committed |
Fix Released |
|