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.
Description of problem:
Restore of incremental backup taken from RHEL7-based Satellite 6.11 on RHEL8-based Satellite 6.11 fails with an error like this, leaving Satellite server in broken state:
--------------------------------------------------------------------------------
REINDEX databases:
- Reindexing the databases [FAIL]
Failed executing runuser - postgres -c "reindexdb -a", exit status 1:
reindexdb: error: could not connect to database template1: FATAL: could not open file "base/1/167655": No such file or directory
--------------------------------------------------------------------------------
Version-Release number of selected component (if applicable):
Red Hat Satellite 6.11.x
How reproducible:
Always.
Steps to Reproduce:
1. Take full offline backup from a RHEL7-based Satellite server.
2. Copy the full backup to and restore it on a newly built RHL8-based Satellite server. The restore completes successfully.
3. Take an incremental offline backup from the RHEL7-based Satellite server.
4. Copy the incremental backup to and restore it on the RHL8-based Satellite server. The restore fails with an error similar to the one in the problem description.
Actual results:
- The restore of the full backup completes successfully.
- The restore of the incremental backup fails with an error similar to the one in the problem description.
Expected results:
Both full and incremental offline backups complete successfully.