Submitter: Jenkins
Branch:    master

commit 039673c2a412282eba9c26f9ff4ac148748ebfb4
Author: Thomas Morin <>
Date:   Mon Sep 19 09:39:57 2016 +0200

    OVS agent: configure both OF10 and OF13
    This change avoids issues where a piece of code restricts
    a bridge to OF13 while there is code still needing OF10, and
    vice-versa, by configuring bridge to both versions.
    This is aimed to be a less complex and easier to merge fix than
    Change-Id: I4475865c4f83cb9f3e12c709af752bc490692ca3
    Closes-Bug: 1622644

** 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.

  OVS agent ryu/native implementation breaks non-OF1.3 uses

Status in networking-bgpvpn:
Status in BaGPipe:
Status in neutron:
  Fix Released

Bug description:
  The ryu-based OVS agent variant forces the bridge Openflow version to 1.3 
only [1], which breaks a few things:
  - troubleshooting tools relying on ovs-ofctl, unless they specify "-O 
Openflow13", will break:
    version negotiation failed (we support version 0x01, peer supports version 
    ovs-ofctl: br-tun: failed to connect to socket (Broken pipe)

  - calling add_flow on an OVSCookieBridge derived from a bridge that is
  an native.ovs_bridge.OVSAgentBridge, will fail with the same error,
  because add_flow will call ovs-ofctl without specifying "-O
  Openflow13"  (this issue is currently hitting networking-bgpvpn: [2])

  It seems like a possible fix would be to not restrict the set of
  Openflow versions supported by the bridge to Openflow13, but to just
  *add* Openflow13 to the set of supported versions.


To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to