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.

in https://github.com/theforeman/foreman_maintain/commit/6f6ebd25029462d7c225d0916bd6aa241a4e67f3 we introduced a way to translate EL7 to EL8 DB backups

but we relied for that on the "foreman_database" feature, which is not available on proxies, which have no foreman and only pulpcore

You end up with errors like:

- Extracting pgsql data                                               [FAIL]    
undefined method `restore_transform' for nil:NilClass

and

/ Extracting pgsql data                                               [FAIL]    
undefined method `postgresql_conf' for nil:NilClass

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

Verified on 6.10.0 snap 16 using rubygem-foreman_maintain-0.8.13 - successfully performed online, offline, incremental online, incremental offline (each with and without pulp data) backup and restore. Also checked 6.9.6 snap 1 that old legacy and new backups (same combinations as above) were restored successfully.

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 (Satellite 6.10 Satellite Maintenance Release), 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/RHBA-2021:4697

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days