[SRU] "Interface monitor is not active" can be observed at ovs-agent start
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Cloud Archive |
Invalid
|
Undecided
|
Unassigned | ||
Mitaka |
Fix Released
|
High
|
Unassigned | ||
neutron |
Fix Released
|
Undecided
|
Hong Hui Xiao | ||
neutron (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
High
|
Unassigned |
Bug 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/
NOTE: the root cause of this issue is that ovsdb monitor async process that neutron-
[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-
ERROR neutron.
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-
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.
Changed in neutron: | |
assignee: | nobody → Hong Hui Xiao (xiaohhui) |
description: | updated |
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 |
tags: | added: sts sts-sru-needed |
description: | updated |
Changed in neutron (Ubuntu): | |
status: | New → Invalid |
Changed in cloud-archive: | |
status: | New → Invalid |
Changed in neutron (Ubuntu Xenial): | |
status: | New → Triaged |
importance: | Undecided → High |
Fix proposed to branch: master /review. openstack. org/319788
Review: https:/