This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2231191 - Using satellite-clone to skip LEAPP as process on Satellite 6.11@RHEL7 to Satellite6.11@RHEL8
Summary: Using satellite-clone to skip LEAPP as process on Satellite 6.11@RHEL7 to Sat...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Clone
Version: 6.12.0
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: Unspecified
Assignee: Akshay Gadhave
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-11 00:41 UTC by Ricardo Santamaria
Modified: 2024-10-05 04:26 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 16:26:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-19789 0 None Migrated None 2024-06-06 16:26:26 UTC

Description Ricardo Santamaria 2023-08-11 00:41:07 UTC 
Description of problem:
Can 'satellite-clone' command be supported to skip  OS LEAPP upgrade in Satellite 6.11

Version-Release number of selected component (if applicable):
Satellite 6.11 on RHEL 7.9 
Fresh RHEL 8

How reproducible:

Following steps shown to be successful: 

Steps to Reproduce:
1. On Satellite 6.11 on RHEL 7 create backup:
  ]# satellite-maintain backup offline --skip-pulp-content /var/backup 

2. On fresh build RHEL 8 make /backup to move the above back to
  ]# mkdir /backup
  ]# ls /backup 
  config_files.tar.gz  metadata.yml  pgsql_data.tar.gz

3. On fresh RHEL8 register  to Customer Portal and enable repositories:
   ]# subscription-manager repos --enable=rhel-8-for-x86_64-baseos-rpms \
--enable=rhel-8-for-x86_64-appstream-rpms \
--enable=satellite-6.11-for-rhel-8-x86_64-rpms \
--enable=satellite-maintenance-6.11-for-rhel-8-x86_64-rpms
  ]# dnf module enable satellite:el8

4. Install satellite-clone:
  ]# dnf -y install satellite-lcone

5. Run satellite-clone

End result is the RH7 Satellite 6.11 database is restored on the RHEL8 server which has as part of running satellite-clone playbook effectively installed fresh Satellite 6.11@RHEL8 and restored the database on. 

Actual results:
Have used satellite-clone to restore database of Satellite 6.11 on RHEL7 to a brand RHEL 8 where Satellite is installed and the backed up database is restored 

Expected results:


Additional info:
Comment 6 Pavel Moravec 2024-01-09 12:56:04 UTC 
Isn't this already fulfilled by:

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.11/html/upgrading_and_updating_red_hat_satellite/migrating-satellite-to-a-new-el-system_upgrade-guide

?
Comment 8 Eric Helms 2024-06-06 16:26:27 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Comment 9 Red Hat Bugzilla 2024-10-05 04:26:32 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Note You need to log in before you can comment on or make changes to this bug.