Bug 1700252

Summary: [OSP14]Default ulimit for nova-compute container is too low when ceph is used
Product: Red Hat OpenStack Reporter: Martin Schuppert <mschuppe>
Component: openstack-tripleo-heat-templatesAssignee: Martin Schuppert <mschuppe>
Status: CLOSED ERRATA QA Contact: Joe H. Rahme <jhakimra>
Severity: medium Docs Contact:
Priority: medium    
Version: 13.0 (Queens)CC: astupnik, dh3, johfulto, mburns, mschuppe, yrabl
Target Milestone: z3Keywords: Triaged, ZStream
Target Release: 14.0 (Rocky)   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-9.3.1-0.20190314162757.d0a6cb1.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1693667 Environment:
Last Closed: 2019-07-02 20:08:28 UTC Type: ---
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: 1693667    
Bug Blocks:    

Description Martin Schuppert 2019-04-16 07:49:03 UTC
+++ This bug was initially created as a clone of Bug #1693667 +++

Description of problem:

Patch [1] was used to enforce new default ulimit for nova-compute container, it was set to 1024. Though it is possible to adjust this limit, it is still suboptimal for certain use cases: for example, when ceph is configured for ephemeral storage and every instance has a huge number of disks.

In such case default limit is wrong and we have to either adjust it manually using the doc, or change default value. I suggest to increase default value to 1048576 (was configured in RHOSP 12).

Symptom:

237794 <... socket resumed> )     = -1 EMFILE (Too many open files)


[1] https://review.openstack.org/#/c/560991/

Comment 7 errata-xmlrpc 2019-07-02 20:08:28 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:1672