Bug 1384260

Summary:	[BUG] Performance tuning settings for foreman-ssl and puppet are lost during upgrade
Product:	Red Hat Satellite	Reporter:	Muhammad Selim Jahangir <mjahangi>
Component:	Upgrades	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Katello QA List <katello-qa-list>
Severity:	medium	Docs Contact:
Priority:	high
Version:	6.2.0	CC:	bbuckingham, jcallaha, stbenjam, xdmoon
Target Milestone:	Unspecified	Keywords:	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:	2017-02-06 21:27:11 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 Muhammad Selim Jahangir 2016-10-13 00:23:10 UTC

Description of problem:
Applying the tuning for large deployments as per Appendix A of the installation manual, "Increasing Concurrent Content Host Registrations" steps 3 and 4 state:

(3) Edit the Foreman Passenger application configuration file /etc/httpd/conf.d/05-foreman-ssl.conf
(4) Edit the Puppet Passenger application configuration file /etc/httpd/conf.d/25-puppet.conf

These two files are managed by puppet within the Satellite/Capsule installer, so changes applied for performance tuning are lost when the satellite-installer is run to reconfigure or upgrade the Satellite.
Manual re-application of the tuning and additional restart of the applications is required following an upgrade to ensure the tuning parameters are in place.

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

Satellite/Capsule 6.2.z on RHEL7

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
After upgrade the tuning parameters are not in the place , it goes back to the default.

Expected results:
After upgrade the tuning parameters should be in place.

Additional info:

Comment 2 Muhammad Selim Jahangir 2017-01-24 05:49:43 UTC

Hi,
Can I request to assign engineer for this Bugzilla please ? 

Selim Jahangir
Technical Support Engineer
Global Support Services
Red Hat, Asia-Pacific"

Comment 3 Stephen Benjamin 2017-02-06 21:27:11 UTC

These passenger settings are now the default.

*** This bug has been marked as a duplicate of bug 1163452 ***

Comment 4 Stephen Benjamin 2017-02-14 00:17:59 UTC

Just a comment about the duplication of this bug, this is largely solved by 1163452, as the new settings work for most workloads.  For tuning in extremely large environments, you can make use of this which will ship in 6.2.8:

  https://bugzilla.redhat.com/show_bug.cgi?id=1305782#c14



The settings that would go in /etc/foreman-installer/custom-hiera.yaml would be something like this, depending on what you need to adjust:


---
apache::mod::passenger::passenger_max_pool_size: 12
apache::mod::passenger::passenger_max_instances_per_app: 6
apache::mod::passenger::passenger_max_request_queue_size: 250
apache::mod::passenger::passenger_stat_throttle_rate: 120

Comment 5 Stephen Benjamin 2017-02-14 00:18:17 UTC

Those changes in the custom-hiera.yaml will persist across installer runs.