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.
DescriptionJulio Entrena Perez
2017-05-10 13:21:50 UTC
Created attachment 1277618[details]
2016 - Performance & Scale Tuning of Satellite 6.2 and Capsules
Description of problem:
Pages 24 and 25 of the performance and scale tuning guide for Satellite 6.2 available at https://access.redhat.com/articles/2626101 suggest to customise the following PostgreSQL settings:
- /var/lib/pgsql/data/postgresql.conf
shared_buffers
max_connections
Currently when the installer runs, for example when upgrading to the next minor release, these customisations are wiped and replaced with the default values.
There does not seem to be any way of persisting these changes across executions of the installer in file /etc/foreman-installer/custom-hiera.yaml .
This results in minor upgrades bringing back previous issues if customers aren't vigilant and re-apply the changes after each upgrade.
We should provide a way to persist these changes in /etc/foreman-installer/custom-hiera.yaml
Version-Release number of selected component (if applicable):
foreman-installer-1.11.0.15-2.el7sat
How reproducible:
Always
Steps to Reproduce:
1. Customise the settings as per above
2. Run "satellite-installer --scenario satellite --upgrade"
3. Check for the previously applied customisations
Actual results:
Customisations are gone.
Expected results:
Customisations are there after the execution of the installer.
Additional info: