Bug 2231191

Summary:	Using satellite-clone to skip LEAPP as process on Satellite 6.11@RHEL7 to Satellite6.11@RHEL8
Product:	Red Hat Satellite	Reporter:	Ricardo Santamaria <risantam>
Component:	Satellite Clone	Assignee:	Akshay Gadhave <agadhave>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	high
Version:	6.12.0	CC:	agadhave, ahumbe, ehelms, gsulliva, mkalyat, momran, pmoravec, rlavi, tharring
Target Milestone:	Unspecified	Keywords:	Documentation, MigratedToJIRA, Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 16:26:27 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 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