Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1600075 - [day2]SSH public key authentication needs to be configured within the newly added hosts
Summary: [day2]SSH public key authentication needs to be configured within the newly a...
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: doc-Maintaining_RHHI
Version: rhhiv-1.5
Hardware: x86_64
OS: Linux
Target Milestone: ---
: RHHI-V 1.5
Assignee: Laura Bailey
Depends On:
Blocks: 1534399
TreeView+ depends on / blocked
Reported: 2018-07-11 11:25 UTC by SATHEESARAN
Modified: 2018-12-17 09:32 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-12-17 09:32:21 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description SATHEESARAN 2018-07-11 11:25:43 UTC
Description of problem:
Due to the limitation of sanity check script, the newly added hosts should have SSH public key authentication from the first new host to other hosts.

For example. Let us take host1, host2, host3 form the cluster POD. Now admin prefers to expand this cluster, with 3 more nodes host4, host5, host6. In this case, admin need to SSH public key authentication from host4 -> host4, host4 -> host5, host4-> host6

Version-Release number of selected component (if applicable):
RHHI 2.0 Day2 doc

Expected results:
Add documentation that there should be a SSH public key authentication from the following hosts:
1. First host in the cluster to all the hosts ( including the same host, and nodes to be expanded )
2. First host in the newly added set of 3 nodes to all the newly added nodes( including the self )

Note You need to log in before you can comment on or make changes to this bug.