With the current behavior, insert-buckets doesn't automatically allocate non-overlapping bucket ids. This could be considered a bug in the documentation or in the code. It would be more user-friendly to consider a bug in the code and fix it in ovs-ofctl, but that's a bigger job than just fixing the crash as these commits do.
On Thu, Sep 10, 2015 at 02:51:03PM -0700, Ray Li wrote: > According to ovs-ofctl's man page, if no bucket_id is specified it's > support to allocate one. Is that not being done? Or is that the bug itself? > > On Thu, Sep 10, 2015 at 1:21 PM, Ben Pfaff <b...@nicira.com> wrote: > > > On Thu, Sep 10, 2015 at 11:46:16AM -0700, Ray Li wrote: > > > Does OVS 2.4 support ovs-ofctl insert-buckets? > > > > > > I just upgraded to OVS 2.4.0, and here's what I tried to do: > > > > > > ovs-vsctl set bridge br0 > > > > > protocols=OpenFlow10,OpenFlow11,OpenFlow12,OpenFlow13,OpenFlow14,OpenFlow15 > > > > > > ovs-ofctl add-group br0 group_id=0,type=all,bucket="actions=output:10" -O > > > OpenFlow11 > > > > > > ovs-ofctl dump-groups br0 -O OpenFlow11 > > > (which shows the groups table correctly with a single bucket) > > > > > > ovs-ofctl insert-buckets br0 > > > group_id=0,command_bucket_id=last,bucket="actions=output:1" -O OpenFlow15 > > > > > > ovs-ofctl dump-groups br0 -O OpenFlow11 > > > (This then hangs indefinitely) > > > > It's a bug, thanks for reporting it. > > > > The underlying problem is that in both cases no bucket_id was specified, > > so it defaults to the same value in each case, and duplicate bucket IDs > > were not correctly handled. You can avoid the problem by specifying a > > different bucket_it in your "insert-buckets" command. > > > > I posted a fix. You can test it by applying the following two patches, > > in this order: > > http://openvswitch.org/pipermail/dev/2015-September/059865.html > > http://openvswitch.org/pipermail/dev/2015-September/059864.html > > _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss