Bug 1696713

Summary:	[THT]Default ulimit value for neutron containers (DHCP, L3 and OVS agents) limits a number of SDN entities in production environment
Product:	Red Hat OpenStack	Reporter:	Alex Stupnikov <astupnik>
Component:	openstack-tripleo-heat-templates	Assignee:	Slawek Kaplonski <skaplons>
Status:	CLOSED ERRATA	QA Contact:	Roee Agiman <ragiman>
Severity:	high	Docs Contact:
Priority:	high
Version:	13.0 (Queens)	CC:	amuller, bhaley, dh3, mburns, slinaber
Target Milestone:	z7	Keywords:	Triaged, ZStream
Target Release:	13.0 (Queens)
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-8.3.1-35.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-07-10 13:03:20 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:

Description Alex Stupnikov 2019-04-05 13:25:58 UTC

Description of problem:

TripleO sets ulimits for different containers since RHOSP 13 [1].
Default value for neutron services and nova-compute is 1024. This
default doesn't work well for nova-compute with huge number of attached
disks, so I have reported bug [2].

Today customer informed me that neutron services are ALSO AFFECTED:
he faced issues with DHCP agents after creating 250 tenant networks
(quite low number) and was able to solve them after increasing default
ulimit value by defining DockerNeutronDHCPAgentUlimit.

I have asked neutron developers to provide recommendations for defaults for the following parameters and was told to report the bug:

DockerNeutronDHCPAgentUlimit
DockerNeutronL3AgentUlimit
DockerOpenvswitchUlimit

[1] https://review.openstack.org/#/c/560991/
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1693667

Comment 1 Slawek Kaplonski 2019-04-18 06:01:28 UTC

Patches backported to stable/queens and stable/rocky branches. Should be synced in next z-stream release.

Comment 12 errata-xmlrpc 2019-07-10 13:03:20 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-2019:1738