With the recent commits it seems that the gate-tempest-dsvm-networking-ovn is succeeding more or less every time. The DBDeadlock issues still are seen on q-svc logs but are not frequent enough to cause ovsdb failures that were leading to the dsvm-networking failing before.
Once in a while a test fails for e.g. tempest.api.network.test_dhcp_ipv6.NetworksTestDHCPv6.test_dhcpv6_two_subnets that failed recently in Jenkins. But I am pretty sure it will succeed if the suite is re-run. Should the gate-tempest-dsvm-networking-ovn become voting at this time, and re-run/re-check if it fails in the Jenkins check? Amitabha From: Russell Bryant <[email protected]> To: [email protected] Date: 08/26/2015 06:24 AM Subject: Re: [openstack-dev] [neutron][networking-ovn][tempest] devstack: gate-tempest-dsvm-networking-ovn failures in Openstack CI On 08/25/2015 03:02 PM, Assaf Muller wrote: > > > On Tue, Aug 25, 2015 at 2:15 PM, Russell Bryant <[email protected] > <mailto:[email protected]>> wrote: > > On 08/25/2015 01:26 PM, Amitabha Biswas wrote: > > Russell suggested removing the MYSQL_DRIVER=MySQL-python declaration > > from local.conf https://review.openstack.org/#/c/216413/which > results in > > PyMySQL as the default. > > > > With the above change the above DB errors are no longer seen in my local > > setup, > > It's great to hear that resolved the errors you saw! > > > 1. Is there any impact of using PyMySQL for the Jenkins check and > gates. > > As Jeremy mentioned, this is what everything else is using (and what OVN > was automatically already using in OpenStack CI). > > > 2. Why is the gate-networking-ovn-python27**failing (the past > couple of > > commits) in {0} > > networking_ovn.tests.unit.test_ovn_plugin.TestOvnPlugin.test_create_port_security > > [0.194020s] ... FAILED. Do we need another conversation to track this? > > This is a separate issue. The networking-ovn git repo has been pretty > quiet the last few weeks and it seems something has changed that made > our tests break. We inherit a lot of base plugin tests from neutron, so > it's probably some change in Neutron that we haven't synced with yet. I > haven't had time to dig into it yet. > > > This patch was recently merged to Neutron: > https://review.openstack.org/#/c/201141/ > > Looks like that unit test is trying to create a port with an invalid MAC > address. > I pushed a fix here: > https://review.openstack.org/#/c/216837/ Thanks, Assaf! Much appreciated! :-) -- Russell Bryant __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
