Bug 1782246

Summary:	OVN Octavia provider driver cannot start new thread after some API activity
Product:	Red Hat OpenStack	Reporter:	Maciej Józefczyk <mjozefcz>
Component:	python-networking-ovn	Assignee:	Maciej Józefczyk <mjozefcz>
Status:	CLOSED ERRATA	QA Contact:	Roman Safronov <rsafrono>
Severity:	high	Docs Contact:
Priority:	high
Version:	16.0 (Train)	CC:	apevec, jlibosva, lhh, majopela, mrunge, scohen
Target Milestone:	z1	Keywords:	Triaged
Target Release:	16.0 (Train on RHEL 8.1)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-networking-ovn-7.1.0-0.20200117101453.810ad54.el8ost	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-03 09:41:29 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1614299, 1676631, 1703958, 1792667, 1874874

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