Bug 1588659

Summary:	[rfe] allow setting fs.aio-max-nr 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:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.3.1	CC:	cduryee, ehelms, pgagne, riehecky, zhunting
Target Milestone:	Unspecified	Keywords:	FieldEngineering, FutureFeature, PrioBumpField
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:	2018-10-09 15:20:39 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-07 17:05:46 UTC

Description of problem:

Currently, if you have a large number of content hosts you may need to edit /etc/sysctl.conf and set fs.aio-max-nr to a larger value. Right now you have to do this manually, but it would be better if it was configured via custom-hiera.yaml so all the config changes can go in one place.

https://access.redhat.com/solutions/1425893 has more info about this.

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

Comment 5 Eric Helms 2018-10-09 15:20:39 UTC

We believe that a customer should configure this option themselves given we do not manage the systctl.d configuration today.

Comment 6 Red Hat Bugzilla 2023-09-15 00:09:53 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days