yahoo-eng-team team mailing list archive

[OpenStack Infra <1768990@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/566178
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=85b46cd51ebec67d5018d8bef4f796ee5ef4fedf
Submitter: Zuul
Branch:    master

commit 85b46cd51ebec67d5018d8bef4f796ee5ef4fedf
Author: Sławek Kapłoński <slawek@xxxxxxxxxxxx>
Date:   Fri May 4 00:12:03 2018 +0200

    Monitor phys_bridges to reconfigured it if created again
    
    In case when external bridge configured in OVS agent's bridge_mappings
    will be destroyed and created again (for example by running ifup-ovs
    script on Centos) bridge wasn't configured by OVS agent.
    That might cause broken connectivity for OpenStack's dataplane if
    dataplane network also uses same bridge.
    
    This patch adds additional ovsdb-monitor to monitor if any
    of physical bridges configured in bridge_mappings was created.
    If so, agent will reconfigure it to restore proper openflow rules
    on it.
    
    Change-Id: I9c0dc587e70327e03be5a64522d0c679665f79bd
    Closes-Bug: #1768990


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

Title:
  OVS agent not reconfigure ext-bridge in case when it was removed and
  created again by administrator

Status in neutron:
  Fix Released

Bug description:
  Neutron OVS agent will configure phys_bridges only during agent start process.
  If later someone remove and create such bridge again it will clean all flows from it.
  Because such bridges are configured with "fail_mode=secure" that might cause to lost of connection in Neutron control plane as it is quite common deployment practice to use same external bridge for data plane and for control plane.

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