Bug 1443688

Summary: [DOC] Detail that if ssh config file does not exist during Ceph Ansible deployment it will need to be created
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Mike Hackett <mhackett>
Component: DocumentationAssignee: Erin Donnelly <edonnell>
Status: CLOSED CURRENTRELEASE QA Contact: Harish NV Rao <hnallurv>
Severity: low Docs Contact:
Priority: low    
Version: 2.2CC: asriram, hnallurv, kdreyer, vashastr
Target Milestone: rc   
Target Release: 2.3   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-06-20 18:22:22 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:
Bug Depends On:    
Bug Blocks: 1437905    

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