← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1836565] [NEW] Functional test test_keepalived_state_change_notification may fail do to race condition

 

Public bug reported:

Functional test
neutron.tests.functional.agent.l3.test_ha_router.L3HATestCase.test_keepalived_state_change_notification
may fail due to setting initial status of keepalived_state during
starting of IP monitor.

Some time ago patch https://review.opendev.org/#/c/642295/ introduced checking initial status of VIP in router's namespace during IPMonitor initialisation process.
It works fine but in this specific test, if keepalived will first set router to master and than IPMonitor will be spawned, enqueue_state_change() function will be called 4 instead of 3 times and test will fail.

Example of failure http://logs.openstack.org/69/668569/3/check/neutron-
functional-python27/9d345e8/testr_results.html.gz

Logstash query:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22line%2048%2C%20in%20test_keepalived_state_change_notification%5C%22

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


** Tags: functional-tests gate-failure l3-dvr-backlog

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

Title:
  Functional test test_keepalived_state_change_notification may fail do
  to race condition

Status in neutron:
  Confirmed

Bug description:
  Functional test
  neutron.tests.functional.agent.l3.test_ha_router.L3HATestCase.test_keepalived_state_change_notification
  may fail due to setting initial status of keepalived_state during
  starting of IP monitor.

  Some time ago patch https://review.opendev.org/#/c/642295/ introduced checking initial status of VIP in router's namespace during IPMonitor initialisation process.
  It works fine but in this specific test, if keepalived will first set router to master and than IPMonitor will be spawned, enqueue_state_change() function will be called 4 instead of 3 times and test will fail.

  Example of failure http://logs.openstack.org/69/668569/3/check
  /neutron-functional-python27/9d345e8/testr_results.html.gz

  Logstash query:
  http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22line%2048%2C%20in%20test_keepalived_state_change_notification%5C%22

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


Follow ups