Bug 1644152

Summary:	Add support of cloning 6.4 satellite
Product:	Red Hat Satellite	Reporter:	Nikhil Kathole <nkathole>
Component:	Satellite Clone	Assignee:	Jonathon Turel <jturel>
Status:	CLOSED ERRATA	QA Contact:	Nikhil Kathole <nkathole>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.5.0	CC:	adujicek, jomitsch, mmccune, zhunting
Target Milestone:	6.4.2	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-02-13 19:07:38 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:	1664350
Bug Blocks:

Description Nikhil Kathole 2018-10-30 06:02:54 UTC

Description of problem:
Its time to add support for 6.4 satellite clone.


Version-Release number of selected component (if applicable):
Satellite 6.5 snap1

satellite-clone-1.2.5-1.el7sat.noarch

How reproducible:
always

Steps to Reproduce:
1.satellite-clone -y

Actual results:
No support for 6.4

Expected results:


Additional info:

https://github.com/RedHatSatellite/satellite-clone/blob/master/library/parse_backup_metadata.py#L21

Comment 3 Ales Dujicek 2018-12-20 13:15:19 UTC

*** Bug 1624433 has been marked as a duplicate of this bug. ***

Comment 7 Mike McCune 2019-01-15 16:37:44 UTC

*** Bug 1666378 has been marked as a duplicate of this bug. ***

Comment 10 Nikhil Kathole 2019-01-25 08:51:57 UTC

VERIFIED

version tested:
Satellite 6.4.2 snap 1
satellite-clone-1.3.1-1.el7sat.noarch

Cloning satellite is successful but satellite-clone could not deal with a backup of the satellite having external databases.

The issue is tracked at https://bugzilla.redhat.com/show_bug.cgi?id=1669229

Comment 13 errata-xmlrpc 2019-02-13 19:07:38 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/RHEA-2019:0344