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.
DescriptionMuhammad 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 2Muhammad 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"
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