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.

Description of problem:
satellite backup should restore /var/lib/pgsql/data/postgresql.conf

Version-Release number of selected component (if applicable):
Satellite 6.4.2

How reproducible:
Always

Steps to Reproduce:
1.Create satellite-backup.
2.Check for the presence of postgresql.conf in the config_files.tar.gz:
# tar zxf /backup/config_files.tar.gz var/lib/pgsql/data/postgresql.conf --to-stdout | cat
tar: var/lib/pgsql/data/postgresql.conf: Not found in archive

Actual results:
postgresql.conf not found

Expected results:
postgresql.conf should be saved in the backup.  Since many old customers directly edited this configuration in the past since custom-hiera.yml support was not there, it is essential to save this in backup for a complete restore later.

Additional info:

Created redmine issue https://projects.theforeman.org/issues/26872 from this bug

Upstream bug assigned to jomitsch

Upstream bug assigned to jomitsch

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26872 has been resolved.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2019:3172