Re: [ovs-discuss] Possible issue/bug at Open vSwitch and ovsdb.

I posted the fix to the mailing list. The patch now include a unit test to cover this bug. https://mail.openvswitch.org/pipermail/ovs-dev/2017-May/332362.html On Thu, May 11, 2017 at 1:16 PM, Andy Zhou wrote: > On Thu, May 11, 2017 at 2:42 AM, Tulio Ribeiro >

Re: [ovs-discuss] Possible issue/bug at Open vSwitch and ovsdb.

On Thu, May 11, 2017 at 2:42 AM, Tulio Ribeiro wrote: > Hi Andy, > > I did the patch but now the command $sudo ovs-vsctl add-br s1 stuck (the > bridge is added but the command does not return). > > The command sudo ovs-vsctl set-controller s1 tcp:192.168.1.215:6653 do

Re: [ovs-discuss] Possible issue/bug at Open vSwitch and ovsdb.

Hi Andy, I did the patch but now the command $sudo ovs-vsctl add-br s1 stuck (the bridge is added but the command does not return). The command sudo ovs-vsctl set-controller s1 tcp:192.168.1.215:6653 do not return as well. The role of a bridge is not defined, which means, the initial role

Re: [ovs-discuss] Possible issue/bug at Open vSwitch and ovsdb.

Hi guys, sorry to bother you again and send this direct message, but I did a test *without* using Mininet, and the problem/behavior persists. Could someone try to test this, please? It is necessary one active controller, I've tested with Floodlight controller. A simple way to verify is,