Bug 1729553 - [OSP13] set default ulimit to nova_libvirt
Summary: [OSP13] set default ulimit to nova_libvirt
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: z8
: 13.0 (Queens)
Assignee: Martin Schuppert
QA Contact: Archit Modi
URL:
Whiteboard:
Depends On: 1728447 1729552
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-12 15:28 UTC by Martin Schuppert
Modified: 2023-03-24 15:04 UTC (History)
7 users (show)

Fixed In Version: openstack-tripleo-heat-templates-8.3.1-57.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1729552
Environment:
Last Closed: 2019-09-03 16:55:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1762455 0 None None None 2019-07-12 15:28:58 UTC
OpenStack gerrit 668457 0 None None None 2019-07-12 15:28:58 UTC
Red Hat Product Errata RHBA-2019:2624 0 None None None 2019-09-03 16:55:48 UTC

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


Note You need to log in before you can comment on or make changes to this bug.