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

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1588193

Summary:	[RFE] allow setting limits.conf via custom-hiera.yaml
Product:	Red Hat Satellite	Reporter:	Chris Duryee <cduryee>
Component:	Installation	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WONTFIX	QA Contact:	Devendra Singh <desingh>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.3.1	CC:	bkearney, cwelton, pgagne, riehecky, stbenjam, zhunting
Target Milestone:	Unspecified	Keywords:	FieldEngineering, FutureFeature, PrioBumpField, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-11-04 14:01:40 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 Chris Duryee 2018-06-06 22:11:43 UTC

Description of problem:

Users commonly need to set limits.conf for httpd and qdrouterd. It should be possible to do this via custom-hiera.yaml, so users don't have to manage the files in a one-off way.

Typical settings are:

# cat /etc/systemd/system/httpd.service.d/limits.conf
[Service]
LimitNOFILE=640000

# cat /etc/systemd/system/qdrouterd.service.d/limits.conf
[Service]
LimitNOFILE=301000

NOTE: I would recommend that these files not be created by default, but only if the user requests it via puppet. Some users may set their limits via other means already, and it would cause a lot of confusion if we interfered with that on a default install.

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

Comment 1 Chris Duryee 2018-06-07 16:52:43 UTC

Please also allow setting of LimitNOFILE for /etc/systemd/system/qpidd.service.d/limits.conf

Comment 2 Stephen Benjamin 2018-07-23 17:37:07 UTC

Qpid should already be possible in 6.3:

qpid::open_file_limit: 10000
qpid::router::open_file_limit: 301000

See https://github.com/theforeman/puppet-qpid/blob/master/manifests/router/service.pp and https://github.com/theforeman/puppet-qpid/blob/master/manifests/service.pp

Comment 3 Bryan Kearney 2019-11-04 14:01:40 UTC

Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.