Bug 1443688 - [DOC] Detail that if ssh config file does not exist during Ceph Ansible deployment it will need to be created
Summary: [DOC] Detail that if ssh config file does not exist during Ceph Ansible deplo...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Documentation
Version: 2.2
Hardware: x86_64
OS: Linux
low
low
Target Milestone: rc
: 2.3
Assignee: Erin Donnelly
QA Contact: Harish NV Rao
URL:
Whiteboard:
Depends On:
Blocks: 1437905
TreeView+ depends on / blocked
 
Reported: 2017-04-19 18:07 UTC by Mike Hackett
Modified: 2017-06-20 18:22 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-20 18:22:22 UTC
Embargoed:


Attachments (Terms of Use)

Description Mike Hackett 2017-04-19 18:07:19 UTC
Description of problem:

In section 2.10 step 3 details modifying the ~/.ssh/config file on the ansible admin node. If this is a fresh ansible install on this node the config file will actually need to be created as it will not exist.

We could re-word step 3 to say:

Modify or create (using a utility such as vi) the ~/.ssh/config file of the Ansible administration node so that Ansible can log in to Ceph nodes as the user you created without requiring you to specify the -u <username> option each time you execute the ansible-playbook command. Replace <username> with the name of the user you created and <hostname> with a host name of a Ceph node: 

Host node1
   Hostname <hostname>
   User <username>
Host node2
   Hostname <hostname>
   User <username>
Host node3
   Hostname <hostname>
   User <username>

After editing or creating the ~/.ssh/config file on the Ansible administration node, ensure the permissions are correct: 

$ chmod 600 ~/.ssh/config

Version-Release number of selected component (if applicable):
RHCS 2.2

Comment 3 John Poelstra 2017-06-20 18:22:22 UTC
Closing this bug as the documentation has been published with the release


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