Ovs monitor tests fail with eventlet timeout
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Unassigned |
Bug Description
Logstash query:
Captured output:
traceback-1: {{{
Traceback (most recent call last):
File "neutron/
output1 = self.collect_
File "neutron/
eventlet.
File "/opt/stack/
hub.switch()
File "/opt/stack/
return self.greenlet.
File "/opt/stack/
sleep_time = wakeup_when - self.clock()
File "/opt/stack/
raise TimeoutException()
fixtures.
}}}
Changed in neutron: | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in neutron: | |
status: | Fix Committed → In Progress |
description: | updated |
summary: |
- functional.agent.test_ovs_flows.ARPSpoofTestCase.test_arp_spoof_disable_port_security - fails + Ovs monitor tests fail with eventlet timeout |
Changed in neutron: | |
assignee: | Maru Newby (maru) → Jeremy Stanley (fungi) |
Changed in neutron: | |
milestone: | none → liberty-1 |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | liberty-1 → 7.0.0 |
The bug is actually with test_killed_ monitor_ respawns( native) , presumably because the increase in ovs functional testing is adding load on the ovs daemon that slows down the testing. Switching to sandboxed ovs instances per test worker might be an option to reduce contention, but for now, I think doubling the test timeout is a good stop-gap.