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
Fixed and merged. Will be available in the next build.
[brick_dirs] is the only option available now. Verified with gdeploy-1.0-9.el7rhgs.noarch
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