Browse Source

Add some wait time between stopping and starting again ovsdb monitor

In functional tests of the ovsdb_monitor, sometimes during high load
of the host where tests are run, "error" message from the killed process
can be received by neutron's async_process after new process was
already spawned.
And that causes failure of the test as new ovsdb_monitor will not
receive events which are expected.

To workaround that issue this patch adds sleep for few seconds between
stopping old and starting new ovsdb_monitor process.

Closes-Bug: #1907068
Change-Id: Ib37a52a623943ae4b6a4ec829c5d12a74514e86c
(cherry picked from commit 0aa7f5b511)
changes/28/778828/1
Slawek Kaplonski 6 months ago
parent
commit
51ba854a0c
1 changed files with 4 additions and 0 deletions
  1. +4
    -0
      neutron/tests/functional/agent/linux/test_ovsdb_monitor.py

+ 4
- 0
neutron/tests/functional/agent/linux/test_ovsdb_monitor.py View File

@ -21,6 +21,7 @@ Tests in this module will be skipped unless:
- sudo testing is enabled (see neutron.tests.functional.base for details)
"""
import time
from oslo_config import cfg
@ -129,6 +130,9 @@ class TestSimpleInterfaceMonitor(BaseMonitorTest):
lambda: self._expected_devices_events(removed_devices, 'removed'))
# restart
self.monitor.stop(block=True)
# NOTE(slaweq): lets give async process few more seconds to receive
# "error" from the old ovsdb monitor process and then start new one
time.sleep(5)
self.monitor.start(block=True, timeout=60)
try:
utils.wait_until_true(


Loading…
Cancel
Save