← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1646526] Re: L2 extensions flows lost on openvswitch restart

 

Reviewed:  https://review.openstack.org/421771
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=ea2cab0e15079490fb772ffa077f5aad236e8239
Submitter: Jenkins
Branch:    master

commit ea2cab0e15079490fb772ffa077f5aad236e8239
Author: Thomas Morin <thomas.morin@xxxxxxxxxx>
Date:   Wed Jan 18 10:50:44 2017 +0100

    openvswitch agent: add OVS_RESTARTED event
    
    This new event is aimed at informing that OVS has restarted, and in particular
    to let L2 extensions know that they may need to setup their flows again.
    
    Change-Id: I9aebe7ccc3e2f565b4339d42842d89b911131b1f
    Closes-Bug: 1646526
    Partial-Bug: 1657689


** 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/1646526

Title:
  L2 extensions flows lost on openvswitch restart

Status in neutron:
  Fix Released

Bug description:
  (taking networking-bgpvpn as an example)

  On an openvswitch restart (desired restart or after a crash), neutron
  openvswitch agent detects the restart, and sets up br-int and br-tun
  again.  However, the base setup for br-tun/br-mpls/br-int integration
  is done only at startup, via the initialize callback of the agent
  extension API.  As a result on openvswitch restart the br-tun flows to
  forward traffic to and from br-mpls are lost, and the BGPVPN
  connectivity is interrupted on the compute node.

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