Red Hat Bugzilla – Bug 1264772
gdeploy: gdeploy expects brick_dirs even when force is enabled over existing brick mounts
Last modified: 2015-11-24 02:09:53 EST
Description of problem: While creating a volume with existing brick mounts, gdeploy expects brick_dirs to be set even when force option is enforced.
Version-Release number of selected component (if applicable):
How reproducible: Always
Steps to Reproduce:
1. Create a config file:
2. Run gdeploy: gdeploy -c gluster.conf
Error: Section 'brick_dirs' or 'mountpoints' not found.
Cannot continue volume creation!
Expected results: Should accept mountpoints values as brick dir when force option is enabled.
This is not a bug. It is the expected behavior. If not doing back-end setup you are supposed to give the brick_dirs, not the mountpoint.
As the documentation of brick_dirs say:
IMP: If only volume creation is to be done and not back-end setup, just
give the relative path of bricks in this section for the hosts specified
in the [hosts] section along with the 'volume' section.
Anush see if you agree with Comment 2, if so I can mark this as not a bug.
Anush, marking this as not a bug. Re-open if you think otherwise.