Bug 1720141

Summary:	Satellite clone should leverage the foreman-maintain restore instead of implementing it's own restore procedure
Product:	Red Hat Satellite	Reporter:	Ivan Necas <inecas>
Component:	Satellite Clone	Assignee:	Jonathon Turel <jturel>
Status:	CLOSED ERRATA	QA Contact:	Vladimír Sedmík <vsedmik>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.6.0	CC:	egolov, jturel
Target Milestone:	6.7.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	satellite-clone-1.5.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-14 13:24:36 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:
Bug Depends On:	1780727
Bug Blocks:

Description Ivan Necas 2019-06-13 08:43:37 UTC

Description of problem:
During investigation and fixing https://bugzilla.redhat.com/show_bug.cgi?id=1716322, we're noticed that the satellite-clone is using it's own restore procedure, which has the following consequences:

1. any fix and enhancement in backup/restore needs to be done twice, or we risk incompatibilities 
2. it would not work with remote databases

Comment 3 Jonathon Turel 2019-09-09 17:28:16 UTC

Created redmine issue https://projects.theforeman.org/issues/27808 from this bug

Comment 6 Vladimír Sedmík 2019-12-06 18:19:11 UTC

Adding dependence on 1780727 as the restore must succeed to ensure the foreman-maintain restore works in the clone scenario.

Comment 10 errata-xmlrpc 2020-04-14 13:24:36 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-2020:1454