yahoo-eng-team team mailing list archive

[OpenStack Infra <1805808@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/620886
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=2ba9e95156d86bc67ecd8440d7343028e89cae3a
Submitter: Zuul
Branch:    master

commit 2ba9e95156d86bc67ecd8440d7343028e89cae3a
Author: Slawek Kaplonski <skaplons@xxxxxxxxxx>
Date:   Thu Nov 29 12:18:17 2018 +0100

    Reinitialize ovs firewall after ovs-vswitchd restart
    
    When ovs-vswitchd process is restarted on host neutron-ovs-agent
    can properly handle that and recover openflows and bridges config.
    But when ovs firewall driver is used, it wasn't reinitialized
    so there were missing some OF rules in br-int and connectivity
    to/from instances was broken.
    
    This patch adds reinitialization of firewall in such case so
    all OF rules are properly reconfigured and connectivity is
    restored.
    
    Change-Id: I8d525bbe48216fef4da890582b8e198933a27833
    Closes-Bug: 1805808


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

Title:
  Openvswitch firewall driver don't reinitialize after ovs-vswitchd
  restart

Status in neutron:
  Fix Released

Bug description:
  When ovs-vswitchd is restarted, neutron-ovs-agent can handle that but
  openvswitch firewall driver will not reinitialize br-int properly and
  because of that connectivity from instance will be broken.

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