Description of problem: ----------------------- Automatic addition of hosts to the cluster feature will work good, only if there is SSH public key authentication for both front-end & backend IPs & FQDNS Version-Release number of selected component (if applicable): ------------------------------------------------------------- RHHI 2.0 deployment docs Expected results: ----------------- Inform user to establish SSH public key authentication from the first host to all the hosts in the cluster ( including the same host ) using: 1. Front-end IP 2. Front-end FQDN ( if exists ) 3. Back-end IP 4. Back-end FQDN ( if exists ) For example: If there are 3 hosts - host1, host2, host3 - in the cluster and deployment will be initiated from host1 then do the following: 1. Generate SSH public & private key on host1 [ root@host1 ]# ssh-keygen 2. Copy the SSH public key to all hosts using front-end IP [ root@host1 ]# ssh-copy-id root@<host1-front-end-ip> [ root@host1 ]# ssh-copy-id root@<host2-front-end-ip> [ root@host1 ]# ssh-copy-id root@<host3-front-end-ip> 3. Copy the SSH public key to all hosts using back-end IP [ root@host1 ]# ssh-copy-id root@<host1-back-end-ip> [ root@host1 ]# ssh-copy-id root@<host2-back-end-ip> [ root@host1 ]# ssh-copy-id root@<host3-back-end-ip> 4. Copy the SSH public key to all hosts using front-end FQDN [ root@host1 ]# ssh-copy-id root@<host1-front-end-FQDN> [ root@host1 ]# ssh-copy-id root@<host2-front-end-FQDN> [ root@host1 ]# ssh-copy-id root@<host3-front-end-FQDN> 5. Copy the SSH public key to all hosts using back-end FQDN [ root@host1 ]# ssh-copy-id root@<host1-back-end-FQDN> [ root@host1 ]# ssh-copy-id root@<host2-back-end-FQDN> [ root@host1 ]# ssh-copy-id root@<host3-back-end-FQDN>
Laura, Its very clearly explained in all those sections. Thanks. Marking this bug as VERIFIED with the given doc links