Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1729553

Summary:	[OSP13] set default ulimit to nova_libvirt
Product:	Red Hat OpenStack	Reporter:	Martin Schuppert <mschuppe>
Component:	openstack-tripleo-heat-templates	Assignee:	Martin Schuppert <mschuppe>
Status:	CLOSED ERRATA	QA Contact:	Archit Modi <amodi>
Severity:	high	Docs Contact:
Priority:	high
Version:	13.0 (Queens)	CC:	amodi, emacchi, jhakimra, mbooth, mburns, mzheng, rhos-maint
Target Milestone:	z8	Keywords:	Triaged, ZStream
Target Release:	13.0 (Queens)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-8.3.1-57.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1729552	Environment:
Last Closed:	2019-09-03 16:55:34 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:	1728447, 1729552
Bug Blocks:

Description Martin Schuppert 2019-07-12 15:28:59 UTC

+++ This bug was initially created as a clone of Bug #1729552 +++

+++ This bug was initially created as a clone of Bug #1728447 +++

Description of problem:
There is an issue in DPDK node as below because of high ulimit in nova_libvirt container and libvirt behavior when closing FD. 
https://bugzilla.redhat.com/show_bug.cgi?id=1721434

Please also consider to set default ulimit for nova_libvirt in heat template file. I can see a patch is provided in upstream, is it possible to include this to downstream version?
https://review.opendev.org/#/c/668416/

Current workaround is in BZ#1721434 comment#59. 


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 13 errata-xmlrpc 2019-09-03 16:55:34 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:2624