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): gdeploy-1.0-12.el6rhs.noarch How reproducible: Always Steps to Reproduce: 1. Create a config file: [hosts] rhshdp03.lab.eng.blr.redhat.com rhshdp04.lab.eng.blr.redhat.com rhshdp05.lab.eng.blr.redhat.com rhshdp06.lab.eng.blr.redhat.com [mountpoints] /gluster1/brick1/ [tune-profile] none [peer] manage=probe [volume] action=create volname=gluster_vol1 replica=yes replica_count=2 force=yes 2. Run gdeploy: gdeploy -c gluster.conf Actual results: 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. Additional info:
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.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days