Bug 1258821

Summary: gdeploy: inconsistency in the way backend setup and volume creation uses brick_dirs value
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Anush Shetty <ashetty>
Component: coreAssignee: Nandaja Varma <nvarma>
Status: CLOSED ERRATA QA Contact: Anush Shetty <ashetty>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rhgs-3.1CC: rhs-bugs, smohan, storage-qa-internal, surs
Target Milestone: ---Keywords: ZStream
Target Release: RHGS 3.1.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: gdeploy-1.0-8 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-10-05 07:25:32 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: 1251815    

Description Anush Shetty 2015-09-01 11:13:57 UTC 
Description of problem: In gdeploy, the backend brick setup and volume creation logic use brick_dirs option names differently. While backend brick setup requires the user to provide [mountpoints] *and* [brick_dir] values, the volume creation insists on [mountpoints] *or* [brick_dirs]

We need to look into two issues here:

1) We need to have a consistent nomenclature for brick paths everywhere: brick_dirs in this case. 

2) Consistency in brick_dirs values: relative or absolute path

Version-Release number of selected component (if applicable): gdeploy-1.0-6.el7rhgs.noarch


How reproducible: Always

1) Config used for backend setup:

[devices]
/dev/vdb

[mountpoints]
/gluster/brick1/

[brick_dir]
s1

2) Config used for volume creation:


[brick_dirs]
/gluster/brick1/vol1

[volume]
action=create
volname=gluster_vol1
Comment 2 Nandaja Varma 2015-09-01 13:25:28 UTC 
Fixed and merged. Will be available in the next build.
Comment 3 Anush Shetty 2015-09-08 09:31:19 UTC 
[brick_dirs] is the only option available now.

Verified with gdeploy-1.0-9.el7rhgs.noarch
Comment 6 errata-xmlrpc 2015-10-05 07:25:32 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-1845.html