Bug 1264772 - gdeploy: gdeploy expects brick_dirs even when force is enabled over existing brick mounts
Summary: gdeploy: gdeploy expects brick_dirs even when force is enabled over existing ...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: gdeploy
Version: rhgs-3.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Sachidananda Urs
QA Contact: Anush Shetty
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-21 07:48 UTC by Anush Shetty
Modified: 2023-09-14 03:05 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-24 07:09:53 UTC
Embargoed:


Attachments (Terms of Use)

Description Anush Shetty 2015-09-21 07:48:21 UTC
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:

Comment 2 Nandaja Varma 2015-09-21 08:15:45 UTC
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.

Comment 3 Sachidananda Urs 2015-11-06 16:38:56 UTC
Anush see if you agree with Comment 2, if so I can mark this as not a bug.

Comment 4 Sachidananda Urs 2015-11-24 07:09:53 UTC
Anush, marking this as not a bug. Re-open if you think otherwise.

Comment 5 Red Hat Bugzilla 2023-09-14 03:05:37 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


Note You need to log in before you can comment on or make changes to this bug.