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.
[RFE] postgres configurations need to be included in variables on Satellite Server in /var/lib/pgsql/data/postgresql.conf and these should be available for customization.
There are various variables which are not included in /var/lib/pgsql/data/postgresql.conf and thus need to add below listed variable at the location in order to address the issues which the Cu faces while running satellite-installer.Is there any way to incorporate the required settings in /var/lib/pgsql/data/postgresql.conf somewhere in the Satellite ?
work_mem = 4MB
shared_buffers = 256MB
max_connections = 500
so satellite-installer will generate the correct /var/lib/pgsql/data/postgresql.conf file when it is run again.
https://access.redhat.com/articles/2951701 includes limited examples for the persistent tuning. However, I lack the expertise to determine how to add the large system tunings from https://access.redhat.com/documentation/en-us/red_hat_satellite/6.2/html/installation_guide/large_deployment_considerations to the persistent settings.
Comment 4Amar Huchchanavar
2017-07-03 17:14:46 UTC
I have customer who would like to make below changes persistent.
>> postgresql.conf :
ssl = on
ssl_ciphers = 'ALL:!ADH:!LOW:!EXP:!MD5:@STRENGTH'
>>pg_hba.conf :
hostssl all postgres 127.0.0.1/32 cert clientcert=1
hostssl all all 127.0.0.1/32 cert clientcert=1
hostssl all all ::1/128 cert clientcert=1
It looks like this was handled as part of https://bugzilla.redhat.com/show_bug.cgi?id=1312098, upstream now has the support for persisting these changes to the Postgres configuration. It should end up in a future version of Satellite.
*** This bug has been marked as a duplicate of bug 1312098 ***
Comment 11Ewoud Kohl van Wijngaarden
2018-06-22 09:42:32 UTC
*** Bug 1312680 has been marked as a duplicate of this bug. ***
Comment 14Julio Entrena Perez
2018-06-28 10:57:42 UTC
*** This bug has been marked as a duplicate of bug 1312098 ***