Bug 1720140

Summary: Backup and restore includes asset files from the original machine, leading to potential UI breakages after restore
Product: Red Hat Satellite Reporter: Ivan Necas <inecas>
Component: Backup & RestoreAssignee: Martin Bacovsky <mbacovsk>
Status: CLOSED ERRATA QA Contact: Lucie Vrtelova <lvrtelov>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.6.0CC: aupadhye, ehelms, vsedmik, zhunting
Target Milestone: 6.6.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: foreman-maintain-0.4.8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-22 19:52:28 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 Ivan Necas 2019-06-13 08:39:31 UTC 
Description of problem:
See https://bugzilla.redhat.com/show_bug.cgi?id=1716322 for description of the symptoms.

Expected:

1. backup doesn't include asset files
2. even if the assets are already included in the backup (when restoring from backup made by tooling prior the fix of this BZ), the restore procedure should exclude this files.
3. given there might be already customers that restored previously the old asset files, we should probably have some procedure in foreman-maintain to clean up (probably by searching for asset files without rpm owner). We should probably run this check as post-upgrade procedure until 6.6 (provided 6.6 would have a fixed version of the restore and satellite-clone)
Comment 5 Martin Bacovsky 2019-06-19 12:07:53 UTC 
Created redmine issue https://projects.theforeman.org/issues/27082 from this bug
Comment 6 Bryan Kearney 2019-08-27 12:07:02 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/27082 has been resolved.
Comment 9 Bryan Kearney 2019-10-22 19:52:28 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, 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