yahoo-eng-team team mailing list archive

[OpenStack Infra <1992953@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/c/openstack/neutron/+/861351
Committed: https://opendev.org/openstack/neutron/commit/8fcf00a36dfcec80bba73b63896d806f48835faf
Submitter: "Zuul (22348)"
Branch:    master

commit 8fcf00a36dfcec80bba73b63896d806f48835faf
Author: Slawek Kaplonski <skaplons@xxxxxxxxxx>
Date:   Fri Oct 14 11:58:02 2022 +0200

    Disable in-band management for bridges before setting up controllers
    
    Disabling in-band management for bridge will effectively disable it for
    all controllers which are or will be set for the bridge. This will
    prevent us from having short time between configuring controller and
    setting connection_mode of the controller to "out-of-band" when
    controller works in the default "in-band" connection mode and adds some
    hidden flows to the bridge.
    
    Closes-Bug: #1992953
    Change-Id: Ibca81eb59fbfad71f223832228f408fb248c5dfa


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

Title:
  Disable in-band flow management in the ovs bridges

Status in neutron:
  Fix Released

Bug description:
  Currently when restarting neutron, neutron do following setup

  a) set controller 127.0.0.1
  b) set out-of-band mode

  between a) and b), ovs runs with in-band mode and it has hidden flow
  in bridge. The hidden flow causing odd dataplane flow.

  To avoid that potensial odd dataplane flow we should do one of below:
  a) configure the controller and set it to out-of-band in a single db transaction, i.e. "ovs-vsctl set-controller br-tenant tcp:127.0.0.1:6633 -- set controller br-tenant connection-mode=out-of-band" or
  b) configure disable-in-band to true for the bridge before configuring the controller, i.e. “ovs-vsctl set bridge br-tenant other-config:disable-in-band=true”

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