yahoo-eng-team team mailing list archive

[Jakub Libosvar <libosvar@xxxxxxxxxx>]

Public bug reported:

If there are multiple ovs-agents instances running on a single node then
trunk re-acts on all ovsdb events. That means if a port is removed from
a trunk bridge then all agents will attempt to clear resources around
given trunk bridge. This leads to race condition where foreign ovs-
agents removes trunk bridge before the correct one. As foreigh ovs-
agents have different integration bridge names, they don't clear up
properly patch ports on br-int side.

Example of failure: http://logs.openstack.org/30/453330/5/check/gate-
neutron-dsvm-fullstack-ubuntu-xenial/b70b50c/testr_results.html.gz

e-r-q:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22still%20has%20following%20ports%20while%20some%20of%20them%20are%20patch%20ports%20for%20trunk%20that%20were%20supposed%20to%20be%20removed%5C%22%20AND%20tags%3Aconsole

33 hits in 7 days

** Affects: neutron
     Importance: Undecided
     Assignee: Jakub Libosvar (libosvar)
         Status: New


** Tags: fullstack gate-failure

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1687709

Title:
  fullstack: ovs-agents remove trunk bridges that don't belong to them

Status in neutron:
  New

Bug description:
  If there are multiple ovs-agents instances running on a single node
  then trunk re-acts on all ovsdb events. That means if a port is
  removed from a trunk bridge then all agents will attempt to clear
  resources around given trunk bridge. This leads to race condition
  where foreign ovs-agents removes trunk bridge before the correct one.
  As foreigh ovs-agents have different integration bridge names, they
  don't clear up properly patch ports on br-int side.

  Example of failure: http://logs.openstack.org/30/453330/5/check/gate-
  neutron-dsvm-fullstack-ubuntu-xenial/b70b50c/testr_results.html.gz

  e-r-q:
  http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22still%20has%20following%20ports%20while%20some%20of%20them%20are%20patch%20ports%20for%20trunk%20that%20were%20supposed%20to%20be%20removed%5C%22%20AND%20tags%3Aconsole

  33 hits in 7 days

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