Bug 533333

Description of problem:
The Installation Guide describes a method to clone an existing Satellite in preparation for failover/HA.  The description is incorrect at step number 5

Version-Release number of selected component (if applicable):
Edition 5.3.0 of Installation Guide for RHN Satellite

How reproducible:
100%

Steps to Reproduce:
Follow guide and end up having clients unable to connect to a cloned Satellite with SSL
  
Actual results:
Clients fail to 'trust' the cloned Satellite

Expected results:
Clients should connect to and trust the cloned Satellite..


Additional info:

The relevant section quoted:

"If the primary Satellite fails, transfer the SSL certificates from it to the secondary. Refer to the Deploying the CA SSL Public Certificate to Clients section of the RHN Client Configuration Guide for precise instructions. "

That is not correct. We need to transfer the ssl key pair package from the main Satellite to the Standby Satellite, as discussed in the backup section:

http://www.redhat.com/docs/en-US/Red_Hat_Network_Satellite/5.3/Installation_Guide/html/s1-maintenance-backup.html

This way all the clients will have the correct _trusted_ certificate installed and will not require any changes.

The Installation Guide step 5 of "8.5. Cloning the Satellite with Embedded DB" should read:

"5 If the primary Satellite fails, transfer the SSL key pair RPM package in /root/ssl-build from the main to the cloned Satellite, and install the package. This ensures that RHN clients will _trust_ the standby/cloned Satellite."