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:

Add support for satellite 6.6 clone

# cat /usr/share/satellite-clone/library/parse_backup_metadata.py | grep SUPPORTED
SUPPORTED_VERSIONS = ["6.2", "6.3", "6.4", "6.5"]

Version-Release number of selected component (if applicable):
Satellite 6.7 snap 1

# rpm -q satellite-clone
satellite-clone-1.4.2-1.el7sat.noarch

How reproducible:
always

Steps to Reproduce:
1. yum install satellite-clone
2. satellite-clone -y


Actual results:


Expected results:


Additional info: Bump new version with https://github.com/RedHatSatellite/satellite-clone/pull/365

Hi Jonathon,

I believe this work has been completed with [1].

Can you confirm?  Is there any additional work needed or should we move this one to POST?

Thanks!

[1] https://github.com/RedHatSatellite/satellite-clone/pull/365

This is completed, so moving to POST

While it is completed, there is no release containing this fix. Can you make a release happen please? :)

Added a card to our team board to request a new release.

Adding dependence on 1780727 as the restore must succeed first to ensure the cloning fully works for 6.6

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