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.
Bug 1421636 - [RFE] Satellite installer pga_hba.conf and postgresql.conf management
Summary: [RFE] Satellite installer pga_hba.conf and postgresql.conf management
Keywords:
Status: CLOSED DUPLICATE of bug 1305782
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.2.6
Hardware: x86_64
OS: Linux
medium
low
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-13 10:22 UTC by Marcel Gazdík
Modified: 2020-07-16 09:12 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-16 14:43:18 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Marcel Gazdík 2017-02-13 10:22:04 UTC 
Add options for satellite installer which will make foreman-db-management more granular. Specifically, disable modification of pg_hba.conf and in that case show a message that certain code has to be added into that file manually if it was not added in one of the previous iteration.

  Possible reasons for that:

    1) Customer would like to add access for remote machines.
       - remote monitoring, etc.
    2) Any other security policy on site.

  Current satellite versions allow the user to install PostgreSQL using the satellite installer with default configuration required for running the Satellite. Customers needs to modify the configuration files in order to comply their company policies and whenever they re-run the satellite installer the modified config files are being overwritten by it. 
  Possible workarounds like using externally managed PostgreSQL or adding immutable flags is not good enough because this solution is not bullet prove when it comes to applying required changes which may come with future Satellite releases and/or it leads always to error messages whenever the satellite-installer is being executed.
Comment 3 Stephen Benjamin 2017-02-16 14:43:18 UTC 
Hi there,

In the case, the customer edited the puppet modules directly. That will never be supported.  However, the class parameter values can be changed using custom hiera with BZ1305782. 

https://bugzilla.redhat.com/show_bug.cgi?id=1305782#c14 explains how to use the hiera feature - it will most likely be available in 6.2.8.

As far as the pg_hba.conf setting, they can set the value like this:

---
postgresql::server::manage_pg_hba_conf: false

The module's documentation indicates it should be changed in the server class, not the globals class.  That documentation is available at https://forge.puppet.com/puppetlabs/postgresql for the postgresql module.

Be aware that modifying the configuration that Satellite ships may have unintended consequences, and it's recommended to test everything in a 
non-production environment first.  


Hope that helps

Stephen

*** This bug has been marked as a duplicate of bug 1305782 ***
Note You need to log in before you can comment on or make changes to this bug.