Bug 1051993

Summary: [RFE] Force argument is ambiguous
Product: [Community] GlusterFS Reporter: purpleidea
Component: cliAssignee: bugs <bugs>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: mainlineCC: amukherj, bugs, jasan, joe, purpleidea, sasundar
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-05 03:48:43 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:

Description purpleidea 2014-01-13 04:34:05 UTC
Description of problem:

As described here:
https://lists.gnu.org/archive/html/gluster-devel/2014-01/msg00097.html



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 purpleidea 2014-03-20 04:52:24 UTC
I came across this issue while working on Puppet Gluster...

volume create: puppet: failed: The brick
annex1.example.com:/var/lib/puppet/tmp/gluster/data/puppet is is being
created in the root partition. It is recommended that you don't use
the system's root partition for storage backend. Or use 'force' at the
end of the command if you want to override this behavior.

For automation purposes, this is a problem, because while I'm happy to
add in the 'force' argument for all commands to avoid the above error,
if a different type of error that can be overrided by force occurs,
then I'll be unknowingly allowing it.

For this reason, it probably makes sense to add in an alternate
syntax, such as --allow-root-storage or similar... One for each
possible override.

Also:

As a side note, I would _LOVE_ to see an --allow-reusing-prefix to
forcibly clear the prefixes if they are empty and create the volume.
The problem is failed gluster volume create commands make folders on
all the hosts, and cause you to hit the prefix problem.

Cheers,
James

Comment 2 Ján Sáreník 2015-12-03 19:06:53 UTC
Ehm. Any update on this?

Comment 3 Atin Mukherjee 2018-10-05 03:48:43 UTC
This is something what we have taken into account in glusterd2. we'll have explicit flags instead of a generic 'force' flag to bypass certain validations. This enhancement will not be worked at glusterd1.