Bug 2172610
| Summary: | "Chapter 3. Cloning Satellite Server" of "Administering Red Hat Satellite" contains 6.12 repo information instead of 6.13 | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Sayan Das <saydas> |
| Component: | Documentation | Assignee: | Adam Lazik <alazik> |
| Documentation sub component: | default | QA Contact: | |
| Status: | CLOSED CURRENTRELEASE | Docs Contact: | |
| Severity: | high | ||
| Priority: | high | CC: | alazik, mdolezel |
| Version: | 6.13.0 | Keywords: | Triaged |
| Target Milestone: | Unspecified | ||
| Target Release: | Unused | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-05-03 20:51:39 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
Sayan Das
2023-02-22 17:39:33 UTC
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. 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 |