yahoo-eng-team team mailing list archive

[OpenStack Infra <1687709@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/517598
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=806cf71eb5af34359f8bc0c6b740752e53cf854f
Submitter: Zuul
Branch:    master

commit 806cf71eb5af34359f8bc0c6b740752e53cf854f
Author: Sławek Kapłoński <slawek@xxxxxxxxxxxx>
Date:   Fri Nov 3 09:59:04 2017 +0000

    Fullstack: init trunk agent's driver only when necessary
    
    Trunk driver is not needed to be initialized when "trunk"
    service plugin is not enabled.
    On production environments it's not possible to base on
    "service_plugins" config option on L2 agent's side so this
    driver is initialized always.
    It cause problems on fullstack tests becasue there is race
    condition between different ovs agents which consumes events
    from Openvswitch monitor.
    On fullstack tests however we can assume that agent's and server's
    config are in sync so trunk driver can be initialized only if
    "trunk" service plugin is enabled on server side.
    
    Change-Id: I3ad8d6e7b8f103867ee277078d03f3a01c20ac0d
    Closes-Bug: #1687709


** Changed in: neutron
       Status: In Progress => Fix Released

-- 
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:
  Fix Released

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