← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 2045757] [NEW] Race condition while waiting for L2 agent to be DOWN

 

Public bug reported:

In Fullstack tests:
neutron.tests.fullstack.test_ports_rebind.TestVMPortRebind.test_vm_port_rebound_when_L2_agent_revived
and
neutron.tests.fullstack.test_ports_rebind.TestRouterPortRebind.test_vm_port_rebound_when_L2_agent_revived
L2 agent is disabled, test is waiting for agent to be DOWN and then it
tries to create port which is marked as "binding failed" due to dead
agent on the compute node.

In some cases like:
http://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_abf/901827/1/check/neutron-fullstack-with-uwsgi/abf43a8/testr_results.html
or
http://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_607/901894/6/check/neutron-fullstack-with-uwsgi/6071fab/testr_results.html

it may happen that L2 agent is found dead already but immediately after
it is reported like that to the client, it is revived because heartbeat
was just received. In the meantime test's client is creating port
expecting that this port will be failed to bound but it's actually bound
properly and test fails.

** Affects: neutron
     Importance: High
     Assignee: Slawek Kaplonski (slaweq)
         Status: Confirmed


** Tags: fullstack gate-failure

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

Title:
  Race condition while waiting for L2 agent to be DOWN

Status in neutron:
  Confirmed

Bug description:
  In Fullstack tests:
  neutron.tests.fullstack.test_ports_rebind.TestVMPortRebind.test_vm_port_rebound_when_L2_agent_revived
  and
  neutron.tests.fullstack.test_ports_rebind.TestRouterPortRebind.test_vm_port_rebound_when_L2_agent_revived
  L2 agent is disabled, test is waiting for agent to be DOWN and then it
  tries to create port which is marked as "binding failed" due to dead
  agent on the compute node.

  In some cases like:
  http://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_abf/901827/1/check/neutron-fullstack-with-uwsgi/abf43a8/testr_results.html
  or
  http://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_607/901894/6/check/neutron-fullstack-with-uwsgi/6071fab/testr_results.html

  it may happen that L2 agent is found dead already but immediately
  after it is reported like that to the client, it is revived because
  heartbeat was just received. In the meantime test's client is creating
  port expecting that this port will be failed to bound but it's
  actually bound properly and test fails.

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



Follow ups