Bug 1449707 - Persist postgresql customisations from the perf & scaling tuning guide
Summary: Persist postgresql customisations from the perf & scaling tuning guide
Keywords:
Status: CLOSED DUPLICATE of bug 1440879
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.2.9
Hardware: All
OS: Linux
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-10 13:21 UTC by Julio Entrena Perez
Modified: 2023-10-06 17:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-10 13:37:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
2016 - Performance & Scale Tuning of Satellite 6.2 and Capsules (748.67 KB, application/pdf)
2017-05-10 13:21 UTC, Julio Entrena Perez
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1443138 0 medium CLOSED Customizations from the perf & scale tuning guide are wiped on every upgrade 2023-10-06 17:37:02 UTC

Internal Links: 1443138

Description Julio 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:

Comment 2 Stephen Benjamin 2017-05-10 13:37:12 UTC

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


Note You need to log in before you can comment on or make changes to this bug.