yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #92704
[Bug 2033387] [NEW] [FT] "TestMaintenance.test_port_forwarding" randomly failing in call assertion
Public bug reported:
Test "neutron.tests.functional.plugins.ml2.drivers.ovn.mech_driver.ovsdb.test_maintenance.TestMaintenance.test_port_forwarding" is randomly failing during the assertion of the "neutron_lib.callbacks.registry.publish" calls after calling "delete_floatingip_port_forwarding". The method is reporting two calls:
* call('port', 'provisioning_complete', 'L2', payload=<neutron_lib.callbacks.events.DBEventPayload object at 0x7fe9b9912f80>),
* call('port_forwarding', 'after_delete', <neutron.services.portforwarding.pf_plugin.PortForwardingPlugin object at 0x7fe9b3b15ab0>, payload=<neutron_lib.callbacks.events.DBEventPayload object at 0x7fe9b39a7400>)
The first one could be a delayed call from the same test. The proposal
is to specifically test the call we are expecting, that is
('port_forwarding', 'after_delete').
Logs:
https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_8a2/periodic/opendev.org/openstack/neutron/master/neutron-
functional-with-pyroute2-master/8a279fa/testr_results.html
Snippet: https://paste.opendev.org/show/bNlr2vMbWn8i7JCuiF8a/
** Affects: neutron
Importance: Low
Assignee: Rodolfo Alonso (rodolfo-alonso-hernandez)
Status: Triaged
** Changed in: neutron
Importance: Undecided => Low
** Changed in: neutron
Assignee: (unassigned) => Rodolfo Alonso (rodolfo-alonso-hernandez)
** Changed in: neutron
Status: New => Triaged
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2033387
Title:
[FT] "TestMaintenance.test_port_forwarding" randomly failing in call
assertion
Status in neutron:
Triaged
Bug description:
Test "neutron.tests.functional.plugins.ml2.drivers.ovn.mech_driver.ovsdb.test_maintenance.TestMaintenance.test_port_forwarding" is randomly failing during the assertion of the "neutron_lib.callbacks.registry.publish" calls after calling "delete_floatingip_port_forwarding". The method is reporting two calls:
* call('port', 'provisioning_complete', 'L2', payload=<neutron_lib.callbacks.events.DBEventPayload object at 0x7fe9b9912f80>),
* call('port_forwarding', 'after_delete', <neutron.services.portforwarding.pf_plugin.PortForwardingPlugin object at 0x7fe9b3b15ab0>, payload=<neutron_lib.callbacks.events.DBEventPayload object at 0x7fe9b39a7400>)
The first one could be a delayed call from the same test. The proposal
is to specifically test the call we are expecting, that is
('port_forwarding', 'after_delete').
Logs:
https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_8a2/periodic/opendev.org/openstack/neutron/master/neutron-
functional-with-pyroute2-master/8a279fa/testr_results.html
Snippet: https://paste.opendev.org/show/bNlr2vMbWn8i7JCuiF8a/
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2033387/+subscriptions
Follow ups