yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #76687
[Bug 1812872] [NEW] Trunk functional tests can interact with each other
Public bug reported:
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
** Affects: neutron
Importance: Medium
Assignee: Slawek Kaplonski (slaweq)
Status: Confirmed
** Tags: functional-tests trunk
--
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:
Confirmed
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
Follow ups