yahoo-eng-team team mailing list archive

[Slawek Kaplonski <1812872@xxxxxxxxxxxxxxxxxx>]

After more investigation of this issue it's not a bug in fact. I spotted
it in my patch which switches neutron-functional job to zuulv3 syntax
because there was bug in this patch and it spawned all devstack services
on node before functional tests were started. Because of that neutron-
ovs-agent running on node was removing bridge and that caused failure of
some trunk functional tests.

** Changed in: neutron
       Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1812872

Title:
  Trunk functional tests can interact with each other

Status in neutron:
  Invalid

Bug description:
  There are 2 functional tests for trunk ovs handler which can interact
  with each other when running in "wrong" order. Those tests are:

  -
  neutron.tests.functional.services.trunk.drivers.openvswitch.agent.test_ovsdb_handler.OVSDBHandlerTestCase.test_do_not_delete_trunk_bridge_with_instance_ports

  -
  neutron.tests.functional.services.trunk.drivers.openvswitch.agent.test_ovsdb_handler.OVSDBHandlerTestCase.test_cleanup_on_vm_delete

  If test_do_not_delete_trunk_bridge_with_instance_ports is run before
  test_cleanup_on_vm_delete it can call 'handle_trunk_remove' and remove
  bridge which is used for second test. Then test_cleanup_on_vm_delete
  will fail.

  Fortunately for now in gate those tests are run in "good" order so we
  don't see this issue there. I saw it in results of patch
  https://review.openstack.org/#/c/619742/ - see
  http://logs.openstack.org/42/619742/36/check/neutron-
  functional/96f4e9c/testr_results.html.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1812872/+subscriptions