functional tests are filled with POLLIN messages from ovs even when it's not using ovs itself
Bug #1687065 reported by
Ihar Hrachyshka
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Low
|
Terry Wilson | ||
ovsdbapp |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
This test has nothing to do with ovs, but still, it's trashed with POLLIN messages. Probably because some previous test case in the worker initialized ovslib and got a logging thread spinned up.
Ideally, we would not have the thread running in non-ovs scope, meaning we would need some way to kill/disable it when not needed. Maybe a fixture in ovsdbapp for that matter (or ovs lib itself) that would restore the state to pre-init could help. Then we could use the fixture in our base test classes.
Changed in ovsdbapp: | |
status: | New → Confirmed |
Changed in neutron: | |
status: | New → Confirmed |
importance: | Undecided → Low |
tags: | added: functional-tests usability |
tags: | added: logging |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/562385
Review: https:/