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:
foreman-maintain backup and restore commands shall be updated to handle the pulp3 used in 6.10 while still supporting the previous pulp2 used in 6.9 and 6.8

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

Expected results:
appropriate DBs and pulp data are successfully backed up and restored for all combinations of backup types and supported releases

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 6.9.6 snap 1 was checked that old legacy and new backups (same combinations as above) were restored successfully.

Same scenarios passed on 6.10 and 6.9 Capsules too.

Yet there are 2 issues pending for snapshot backups and offline backup on an external DB setup. These will be tracked separately:
Snapshot backup/restore: https://bugzilla.redhat.com/show_bug.cgi?id=1999841
External DB offline backup/restore: https://bugzilla.redhat.com/show_bug.cgi?id=2000971

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