On 24 September 2016 at 09:34, Advith Nagappa <advith.naga...@gmail.com> wrote: > Hello, > > I have installed ovs 2.5.0 on Ubuntu 14.04(Kernel 4.2.0-27-generic) > Virtualbox on a Windows Host. ( I was able to produce the issue for ovs > 2.3.3 and 2.4.0) > > On running 'make check-system-userspace' , all test cases fail. > > Interestingly though, the first time I ran the 'check' on this > datapath-sanity, only ping between two ports was successful. > > datapath-sanity > > 1: datapath - ping between two ports ok > 2: datapath - ping between two ports on vlan FAILED > (system-traffic.at:49) > 3: datapath - ping6 between two ports FAILED > (system-traffic.at:53)VM, > > but on subsequent checks (without re configuring or re-install), everything > fails > > datapath-sanity > > 1: datapath - ping between two ports FAILED > (system-traffic.at:23) > 2: datapath - ping between two ports on vlan FAILED > (system-traffic.at:27) > 3: datapath - ping6 between two ports FAILED > (system-traffic.at:76) > > I noticed that as the check is run, the ethernet connection on my VM gets > disconnected and re-connects once again. This is just an observation, I am > not sure if it is related. > > I have attached the log file for reference. Appreciate your inputs.
Hmm. Thanks for trying this out. I haven't been able to reproduce this, although I am testing with different kernels and using the latest branch-2.5 from git. A couple of things to watch out for - if 'br0' or 'ovs-p0', 'ovs-p1' devices already exist before running the test then these may interfere with the testsuite running properly. In your posted system-userspace-testsuite.log I also see messages like this from the logs: +2016-09-24T16:15:09.493Z|00025|netlink_notifier|WARN|received bad netlink message It seems that this just means that OVS userspace received some netlink message it didn't expect. I'm not sure why it would show up in the userspace tests like this, although it's probably also dependent on which kernel you're running so maybe linux-4.2 in combination with OVS-2.5 often prints this. However, I noticed that these complaints are happening after the test has succeeded, in the final step where OVS is stopped and the logs are checked. So the actual target of the tests has passed, it's just this last log checking that failed. It's not something to be worried about. OVS-2.5 is also the first release to contain these tests, so there may be some teething issues with them like this. I hope that they will be more reliable in the upcoming v2.6 release and beyond. _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
