On 26 February 2016 at 03:57, Ilya Maximets <i.maxim...@samsung.com> wrote: > Fixes failure of test due to not yet fully destroyed ports from > previous test if ovs-vswitchd was killed. > > Example: > > netdev_linux|WARN|br0: creating tap device failed: Device or resource busy > bridge|WARN|could not open network device br0 (Device or resource busy) > > Signed-off-by: Ilya Maximets <i.maxim...@samsung.com>
If I'm not mistaken, this will add over 20 minutes of sleeping to the standard testsuite. Well, less if you're running in parallel, but still not great. Is there a way that we could detect this "device or resource busy" error during perhaps OVS_TRAFFIC_VSWITCHD_START, for example by querying the kernel for br0 device status first, and attempt that a few times (maybe using OVS_WAIT_UNTIL(...)) instead? _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
