Bug 1782246 - OVN Octavia provider driver cannot start new thread after some API activity
Summary: OVN Octavia provider driver cannot start new thread after some API activity
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-networking-ovn
Version: 16.0 (Train)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: z1
: 16.0 (Train on RHEL 8.1)
Assignee: Maciej Józefczyk
QA Contact: Roman Safronov
URL:
Whiteboard:
Depends On:
Blocks: 1614299 1676631 1703958 1792667 1874874
TreeView+ depends on / blocked
 
Reported: 2019-12-11 13:52 UTC by Maciej Józefczyk
Modified: 2020-09-02 13:27 UTC (History)
6 users (show)

Fixed In Version: python-networking-ovn-7.1.0-0.20200117101453.810ad54.el8ost
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-03 09:41:29 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1856550 0 None None None 2019-12-16 11:19:49 UTC
OpenStack gerrit 699188 0 None ABANDONED Cache OvnProviderHelper object in OvnProviderDriver 2020-02-27 14:34:41 UTC
Red Hat Product Errata RHBA-2020:0654 0 None None None 2020-03-03 09:42:08 UTC

Description Maciej Józefczyk 2019-12-11 13:52:25 UTC 
Description of problem:

OVN Octavia provider driver cannot start new thread after some API activity.
Issue spotted on OSP16 containers with OVN Octavia provider driver.

How reproducible:
Run ShiftOnStack tests and check increasing number of threads spawned.
Potentially could be reproduced on devstack with for-loop.

Log-error message:
http://paste.openstack.org/show/787439/
Comment 6 Roman Safronov 2020-02-19 13:22:40 UTC 
Verified on 16.0-RHEL-8/RHOS_TRUNK-16.0-RHEL-8-20200212.n.0 with python3-networking-ovn-7.1.0-0.20200204065607.57ac389.el8ost.noarch

Verified that when creating multiple octavia objects with ovn driver the amount of octavia_wsgi processes on all nodes does not grow.
Comment 8 errata-xmlrpc 2020-03-03 09:41:29 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0654
Note You need to log in before you can comment on or make changes to this bug.