Bug 1859312

Summary: Offline backups are not restored properly, content is missing
Product: Red Hat Satellite Reporter: Vladimír Sedmík <vsedmik>
Component: Satellite MaintainAssignee: Amit Upadhye <aupadhye>
Status: CLOSED ERRATA QA Contact: Vladimír Sedmík <vsedmik>
Severity: high Docs Contact:
Priority: high    
Version: 6.8.0CC: ahumbe, apatel, aupadhye, kgaikwad, mawerner, pcreech
Target Milestone: 6.8.0Keywords: PrioBumpGSS, Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: rubygem-foreman_maintain-0.6.9 Doc Type: Known Issue
Doc Text:
Offline backups are not restored properly, content is missing
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 12:38:24 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Vladimír Sedmík 2020-07-21 17:17:54 UTC
Description of problem:
Restore of the offline backup does not restore the content. It seems to be related to offline backups only, online backups are restored properly.


Version-Release number of selected component (if applicable):
Satellite 6.8 snap 9 (rubygem-foreman_maintain-0.6.8-1.el7sat.noarch)


How reproducible:
always


Steps to Reproduce:
1. Have a Satellite with some content (organization, manifest, synced repos, etc)
2. Create an offline backup, with or without Pulp data
# foreman-maintain backup offline -y /backups/ofl-pulp
3. Restore the backup
# foreman-maintain restore -y /backups/ofl-pulp/satellite-backup-*


Actual results:
The backup and restore succeeds (no errors shown), however, the content is missing.


Expected results:
Content being restored successfully.

Comment 3 Bryan Kearney 2020-07-28 12:05:46 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/30469 has been resolved.

Comment 7 errata-xmlrpc 2020-10-27 12:38:24 UTC
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.8 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-2020:4365