Bug 1319508

Summary: [GSS][Doc-bug]Bogus locations for cephdeploy.conf, in RHCS installation guide.
Product: Red Hat Ceph Storage Reporter: Vimal Kumar <vikumar>
Component: DocumentationAssignee: Bara Ancincova <bancinco>
Status: CLOSED CURRENTRELEASE QA Contact: ceph-qe-bugs <ceph-qe-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.3.2CC: kdreyer, ngoswami, nlevine, vikumar
Target Milestone: rc   
Target Release: 2.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-19 17:18:04 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:

Description Vimal Kumar 2016-03-20 19:32:49 UTC
1) Description of problem:

The RHCS1.3 installation guide in section "1.2.3. Installation by ISO", mentions that 'ice_setup' creates 'cephdeploy.conf' at three locations. From the guide:

"It writes a .cephdeploy.conf file to /root ~ and the current working directory."

From the above sentence, it seems that the file is written to '/root/', '~' ie.. the home folder of the user running the ice_setup utility, and the current working directory.

This should need some clarity. 'ice_setup' utility is suggested to run as root within the 'ceph-config' folder of a normal user created on the machine. Hence, if the user account name is 'cepher', the location from 'ice_setup' should be run will be /home/cepher/ceph-config. 

Hence the file should only be created within /home/cepher/ceph-config and /root/. The documentation needs to be verified and corrected, especially the line "It writes a .cephdeploy.conf file to /root ~ and the current working directory." in the section "1.2.3. Installation by ISO".

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

RHCS1.3 Installation documentation

Comment 2 Neil Levine 2016-03-22 19:16:35 UTC
Given this is ceph-deploy I think this bug needs to be assigned to 1.3.2 or 1.3.3. 

Not sure how post-release, doc-only errata are handled in BZ?