@Carl, I agree that's the reason. Ideally we would kill the contention altogether if every test would have its own external network but that is blocked until we can get rid of the external_network_id config option.
** Changed in: neutron Status: In Progress => Invalid ** Changed in: neutron Milestone: newton-3 => None -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1553374 Title: Intermittent failure in BGP API tests Status in neutron: Invalid Bug description: Seeing the following failure intermittently in API test jobs: http://paste.openstack.org/show/489400/ In the 2 failed jobs [1][2] I've analyzed, test_get_advertised_routes_floating_ips() runs before this failed test. test_get_advertised_routes_null_address_scope() assumes no floating IP associations and no address scopes so that it can assert that no routes are being announced by a bgp_speaker. My theory is that the floating IP created in test_get_advertised_routes_floating_ips() doesn't get cleaned up fast enough, and test_get_advertised_routes_null_address_scope() runs before the floating IP from the previous test has actually been cleaned up. [1] http://logs.openstack.org/85/267985/9/check/gate-neutron-dsvm-api/b09db1c/console.html [2] http://logs.openstack.org/76/282876/17/check/gate-neutron-dsvm-api/b49cae9/console.html To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1553374/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp