On Fri, Feb 03, 2017 at 11:02:39AM +0000, Gabor Locsei wrote:
> Due to an unitialized script variable, we managed to create a bridge with an
> 'empty' name.
>
> ovs-vsctl threw an error but the object was created nonetheless. I reproduced
> the error on different versions.
> To avoid interference with our own code and environment settings, I installed
> 2.6.1 on openSUSE Tumbleweed aarch64 (ARM64).
>
> Expected behaviour: Don't create the bridge/port etc when parsing the object
> name throws an error.
> When the datapath_type is also specified, OVS will start an infinite loop
> trying to add a port (?), increasing load to an extent that makes the system
> almost unresponsive.
> Yes, I'm aware these might be two separate issues.
Thanks for the report. I posted patches to fix these bugs:
https://mail.openvswitch.org/pipermail/ovs-dev/2017-February/328410.html
https://mail.openvswitch.org/pipermail/ovs-dev/2017-February/328411.html
If you have a chance to try out the patches, it would be nice, but I'm
pretty confident in them.
_______________________________________________
discuss mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
