Bug 1937457

Summary: Add command for cloning Satellite with an external database
Product: Red Hat Satellite Reporter: Mike McCune <mmccune>
Component: DocumentationAssignee: satellite-doc-list
Status: CLOSED NOTABUG QA Contact: satellite-doc-list
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.9.0   
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-03-10 22:04:45 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 Mike McCune 2021-03-10 17:03:49 UTC
Document URL: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.8/html/upgrading_and_updating_red_hat_satellite/cloning_satellite_server#sec-Cloning_to_Target

Section Number and Name: 2.4.2

Describe the issue: We need an additional command after step 5 to include installation of require database packages when using an external database during cloning.

Suggestions for improvement:

Add step 6:

5. Install the satellite-clone package

# satellite-maintain packages install satellite-clone

After you install the satellite-clone tool, you can adjust any configuration to suit your own deployment in the /etc/satellite-clone/satellite-clone-vars.yml file. 


6. External Database: Install required database packages

If you are utilizing an external database for Satellite, please install these extra utilities:

# yum -y install rh-mongodb34-syspaths rh-postgresql12-syspaths rh-postgresql12-postgresql-evr