Document URL: https://dxp-docp-prod.apps.ext-waf.spoke.prod.us-west-2.aws.paas.redhat.com/documentation/en-us/red_hat_satellite/6.13/html-single/administering_red_hat_satellite/index?lb_target=preview Section Number and Name: Chapter 3. Cloning Satellite Server Describe the issue: 3.2. Prerequisites ~~ A backup from Satellite 6.12 that you make using the satellite-maintain backup script. You can use a backup with or without Pulp data. ~~ 3.4.2. Cloning to the Target Server Step 4: ~~ # subscription-manager register your_customer_portal_credentials # subscription-manager attach --pool=pool_ID # subscription-manager repos --disable=* # subscription-manager repos --enable=rhel-8-for-x86_64-appstream-rpms \ --enable=satellite-6.12-for-rhel-8-x86_64-rpms \ --enable=satellite-maintenance-6.12-for-rhel-8-x86_64-rpms ~~ We mention the details of 6.12 instead of 6.13 Suggestions for improvement: Ensure that we are mentioning details about 6.13 instead of 6.12 in the highlighted sections. Additional information: NA
Hello Sayan, The Cloning Server chapter is (or rather was) built so that customers can create a backup of their server, which has a previous version, before upgrading to current product version. What surprised me is that it is currently in Administering Satellite, because it used to be in Updating and Upgrading guide where it makes the most sense. After tracing back the PR (https://github.com/theforeman/foreman-documentation/pull/1965) it appears that it was removed from the Upgrading Guide because it was deemed unnecessary by the Stakeholders. So the most logical course of action right now would be to rewrite to chapter to clone the current version of the Satellite server; however; I will need to confirm this with management and other writers. Currently verifying the next course of action. CC @mdolezel
Correct. The reason for raising the bug is the fact that we have the cloning process documented here in the Administration Guide. But cloning is not needed only for upgrades, If someone wants to migrate a Sat 6.13 from one VM to another, Cloning can be used there as well . From that perspective, Upgrade guide of 6.13, can have the cloning instruction for 6.12 But Admnistration guide should have instructions for 6.13 only.
Agreed. I will update this ticket soon with the next steps.
Created PR: https://github.com/theforeman/foreman-documentation/pull/2029
The documentation has been updated to include instructions for cloning the current version of the Satellite server: https://dxp-docp-prod.apps.ext-waf.spoke.prod.us-west-2.aws.paas.redhat.com/documentation/en-us/red_hat_satellite/6.13/html-single/administering_red_hat_satellite/index?lb_target=preview#sec-Cloning_Prerequisites https://dxp-docp-prod.apps.ext-waf.spoke.prod.us-west-2.aws.paas.redhat.com/documentation/en-us/red_hat_satellite/6.13/html-single/administering_red_hat_satellite/index?lb_target=preview#sec-Cloning_to_Target
Updated documentation is now live on RH Customer Portal: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.13/html-single/administering_red_hat_satellite/index#sec-Cloning_Prerequisites https://access.redhat.com/documentation/en-us/red_hat_satellite/6.13/html-single/administering_red_hat_satellite/index#sec-Cloning_to_Target