| 2016-05-23 08:33:05 |
Hong Hui Xiao |
bug |
|
|
added bug |
| 2016-05-23 08:33:12 |
Hong Hui Xiao |
neutron: assignee |
|
Hong Hui Xiao (xiaohhui) |
|
| 2016-05-23 09:11:42 |
OpenStack Infra |
neutron: status |
New |
In Progress |
|
| 2016-08-29 07:28:48 |
OpenStack Infra |
neutron: status |
In Progress |
Fix Released |
|
| 2018-03-28 14:44:07 |
Edward Hope-Morley |
bug task added |
|
neutron (Ubuntu) |
|
| 2018-03-28 14:44:34 |
Edward Hope-Morley |
nominated for series |
|
Ubuntu Xenial |
|
| 2018-03-28 14:44:34 |
Edward Hope-Morley |
nominated for series |
|
Ubuntu Artful |
|
| 2018-03-28 14:45:44 |
Edward Hope-Morley |
bug task added |
|
cloud-archive |
|
| 2018-03-28 14:45:53 |
Edward Hope-Morley |
nominated for series |
|
cloud-archive/mitaka |
|
| 2018-03-28 15:11:56 |
Edward Hope-Morley |
description |
I noticed this error message in neutron-ovs-agent log when start neutron-openvswitch-agent
ERROR neutron.agent.linux.ovsdb_monitor [req-a7c7a398-a13b-490e-adf8-c5afb24b4b9c None None] Interface monitor is not active.
ovs-agent will start ovsdb_monitor at [1], and first use it at [2]. There is no guarantee that ovsdb_monitor is ready at [2]. So, I can see the error when start neutron-openvswitch-agent.
We should block the start to wait for the process to be active, and then use it. Or else, the use of ovsdb_monitor will be meaningless.
[1] https://github.com/openstack/neutron/blob/6da27a78f42db00c91a747861eafde7edc6f1fa7/neutron/agent/linux/polling.py#L35
[2] https://github.com/openstack/neutron/blob/6da27a78f42db00c91a747861eafde7edc6f1fa7/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py#L1994 |
[Impact]
Requesting to backport to Mitaka since we are seeing this issue in Mitaka clouds (and fix landed in Newton) whereby some compute nodes fail to have their flows added to br-tun following restart of openvswitch-switch.
[Test Case]
* Deploy Openstack Mitaka with one compute host
* Create an instance with overlay network (gre)
* Make a note of flows added to br-tun (ovs-vsctl dump-flows br-tun)
* systemctl restart openvswitch-switch
* Check that flows are re-added to br-tun (compare with previous output)
* Ensure you do not see "Interface monitor is not active" in /var/log/neutron/neutron-openvswitch-agent
NOTE: the root cause of this issue is that ovsdb monitor async process that neutron-openvswitch-agent starts takes too long to start and is not active by the time the rpc_loop tries to poll for updates. It is hard to simulate this scenario and as such it is difficult to know whether it has happened and resolved by this patch. Nevertheless this patch is small and known to have resolved the issue for newer versions of Openstack.
[Regression Potential]
---------------
I noticed this error message in neutron-ovs-agent log when start neutron-openvswitch-agent
ERROR neutron.agent.linux.ovsdb_monitor [req-a7c7a398-a13b-490e-adf8-c5afb24b4b9c None None] Interface monitor is not active.
ovs-agent will start ovsdb_monitor at [1], and first use it at [2]. There is no guarantee that ovsdb_monitor is ready at [2]. So, I can see the error when start neutron-openvswitch-agent.
We should block the start to wait for the process to be active, and then use it. Or else, the use of ovsdb_monitor will be meaningless.
[1] https://github.com/openstack/neutron/blob/6da27a78f42db00c91a747861eafde7edc6f1fa7/neutron/agent/linux/polling.py#L35
[2] https://github.com/openstack/neutron/blob/6da27a78f42db00c91a747861eafde7edc6f1fa7/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py#L1994 |
|
| 2018-03-28 15:12:32 |
Edward Hope-Morley |
summary |
"Interface monitor is not active" can be observed at ovs-agent start |
[SRU] "Interface monitor is not active" can be observed at ovs-agent start |
|
| 2018-03-28 15:12:41 |
Edward Hope-Morley |
tags |
|
sts sts-sru-needed |
|
| 2018-03-28 15:26:43 |
Edward Hope-Morley |
attachment added |
|
lp1692397-xenial-mitaka.debdiff https://bugs.launchpad.net/cloud-archive/+bug/1584647/+attachment/5093636/+files/lp1692397-xenial-mitaka.debdiff |
|
| 2018-03-28 15:28:26 |
Corey Bryant |
bug task added |
|
cloud-archive/mitaka |
|
| 2018-03-28 15:28:59 |
Corey Bryant |
bug task added |
|
neutron (Ubuntu Xenial) |
|
| 2018-03-28 15:31:06 |
Edward Hope-Morley |
description |
[Impact]
Requesting to backport to Mitaka since we are seeing this issue in Mitaka clouds (and fix landed in Newton) whereby some compute nodes fail to have their flows added to br-tun following restart of openvswitch-switch.
[Test Case]
* Deploy Openstack Mitaka with one compute host
* Create an instance with overlay network (gre)
* Make a note of flows added to br-tun (ovs-vsctl dump-flows br-tun)
* systemctl restart openvswitch-switch
* Check that flows are re-added to br-tun (compare with previous output)
* Ensure you do not see "Interface monitor is not active" in /var/log/neutron/neutron-openvswitch-agent
NOTE: the root cause of this issue is that ovsdb monitor async process that neutron-openvswitch-agent starts takes too long to start and is not active by the time the rpc_loop tries to poll for updates. It is hard to simulate this scenario and as such it is difficult to know whether it has happened and resolved by this patch. Nevertheless this patch is small and known to have resolved the issue for newer versions of Openstack.
[Regression Potential]
---------------
I noticed this error message in neutron-ovs-agent log when start neutron-openvswitch-agent
ERROR neutron.agent.linux.ovsdb_monitor [req-a7c7a398-a13b-490e-adf8-c5afb24b4b9c None None] Interface monitor is not active.
ovs-agent will start ovsdb_monitor at [1], and first use it at [2]. There is no guarantee that ovsdb_monitor is ready at [2]. So, I can see the error when start neutron-openvswitch-agent.
We should block the start to wait for the process to be active, and then use it. Or else, the use of ovsdb_monitor will be meaningless.
[1] https://github.com/openstack/neutron/blob/6da27a78f42db00c91a747861eafde7edc6f1fa7/neutron/agent/linux/polling.py#L35
[2] https://github.com/openstack/neutron/blob/6da27a78f42db00c91a747861eafde7edc6f1fa7/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py#L1994 |
[Impact]
Requesting to backport to Mitaka since we are seeing this issue in Mitaka clouds (and fix landed in Newton) whereby some compute nodes fail to have their flows added to br-tun following restart of openvswitch-switch.
[Test Case]
* Deploy Openstack Mitaka with one compute host
* Create an instance with overlay network (gre)
* Make a note of flows added to br-tun (ovs-vsctl dump-flows br-tun)
* systemctl restart openvswitch-switch
* Check that flows are re-added to br-tun (compare with previous output)
* Ensure you do not see "Interface monitor is not active" in /var/log/neutron/neutron-openvswitch-agent
NOTE: the root cause of this issue is that ovsdb monitor async process that neutron-openvswitch-agent starts takes too long to start and is not active by the time the rpc_loop tries to poll for updates. It is hard to simulate this scenario and as such it is difficult to know whether it has happened and resolved by this patch. Nevertheless this patch is small and known to have resolved the issue for newer versions of Openstack.
[Regression Potential]
I can't think how this patch could cause a regression. The only possible difference could be that the rpc_loop might take longer to update flows on ovs restart but that in itself would indicate a wider system issue beyond the neutron service that would not constitute a regression.
---------------
I noticed this error message in neutron-ovs-agent log when start neutron-openvswitch-agent
ERROR neutron.agent.linux.ovsdb_monitor [req-a7c7a398-a13b-490e-adf8-c5afb24b4b9c None None] Interface monitor is not active.
ovs-agent will start ovsdb_monitor at [1], and first use it at [2]. There is no guarantee that ovsdb_monitor is ready at [2]. So, I can see the error when start neutron-openvswitch-agent.
We should block the start to wait for the process to be active, and then use it. Or else, the use of ovsdb_monitor will be meaningless.
[1] https://github.com/openstack/neutron/blob/6da27a78f42db00c91a747861eafde7edc6f1fa7/neutron/agent/linux/polling.py#L35
[2] https://github.com/openstack/neutron/blob/6da27a78f42db00c91a747861eafde7edc6f1fa7/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py#L1994 |
|
| 2018-03-28 15:35:41 |
Corey Bryant |
neutron (Ubuntu): status |
New |
Invalid |
|
| 2018-03-28 15:35:47 |
Corey Bryant |
cloud-archive: status |
New |
Invalid |
|
| 2018-03-28 15:35:51 |
Corey Bryant |
cloud-archive/mitaka: status |
New |
Triaged |
|
| 2018-03-28 15:35:54 |
Corey Bryant |
cloud-archive/mitaka: importance |
Undecided |
High |
|
| 2018-03-28 15:35:57 |
Corey Bryant |
neutron (Ubuntu Xenial): status |
New |
Triaged |
|
| 2018-03-28 15:36:01 |
Corey Bryant |
neutron (Ubuntu Xenial): importance |
Undecided |
High |
|
| 2018-03-28 15:47:42 |
Edward Hope-Morley |
attachment removed |
lp1692397-xenial-mitaka.debdiff https://bugs.launchpad.net/cloud-archive/+bug/1584647/+attachment/5093636/+files/lp1692397-xenial-mitaka.debdiff |
|
|
| 2018-03-28 15:48:29 |
Edward Hope-Morley |
attachment added |
|
lp1584647-xenial-mitaka.debdiff https://bugs.launchpad.net/cloud-archive/+bug/1584647/+attachment/5093678/+files/lp1584647-xenial-mitaka.debdiff |
|
| 2018-04-12 09:25:38 |
Łukasz Zemczak |
neutron (Ubuntu Xenial): status |
Triaged |
Fix Committed |
|
| 2018-04-12 09:25:42 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2018-04-12 09:25:47 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2018-04-12 09:25:50 |
Łukasz Zemczak |
tags |
sts sts-sru-needed |
sts sts-sru-needed verification-needed verification-needed-xenial |
|
| 2018-04-17 08:17:50 |
Dominique Poulain |
bug |
|
|
added subscriber Dominique Poulain |
| 2018-04-17 16:29:45 |
Edward Hope-Morley |
tags |
sts sts-sru-needed verification-needed verification-needed-xenial |
sts sts-sru-needed verification-done-xenial verification-needed |
|
| 2018-04-17 16:29:54 |
Edward Hope-Morley |
tags |
sts sts-sru-needed verification-done-xenial verification-needed |
sts sts-sru-needed verification-done verification-done-xenial |
|
| 2018-04-23 10:50:44 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2018-04-23 10:50:43 |
Launchpad Janitor |
neutron (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2018-04-23 12:04:47 |
Corey Bryant |
cloud-archive/mitaka: status |
Triaged |
Fix Committed |
|
| 2018-04-23 12:04:50 |
Corey Bryant |
tags |
sts sts-sru-needed verification-done verification-done-xenial |
sts sts-sru-needed verification-done verification-done-xenial verification-mitaka-needed |
|
| 2018-06-01 13:01:53 |
Edward Hope-Morley |
tags |
sts sts-sru-needed verification-done verification-done-xenial verification-mitaka-needed |
sts sts-sru-needed verification-done verification-done-xenial verification-mitaka-done |
|
| 2018-06-01 14:13:01 |
Corey Bryant |
cloud-archive/mitaka: status |
Fix Committed |
Fix Released |
|
