Bug 1569256

Summary: Unable to create gluster volume
Product: [Community] GlusterFS Reporter: gzcwnk <thing.thing>
Component: libglusterfsclientAssignee: bugs <bugs>
Status: CLOSED EOL QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.0CC: bugs
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-20 18:29:23 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 gzcwnk 2018-04-18 22:29:57 UTC 
Description of problem:

Following documentation and I get this un-expected qualification that according to docs isnt what I expect.

===========
[root@glustep1 ~]# gluster volume create gv0 replica 2 glusterp1:/bricks/brick1/gv0 glusterp2:/bricks/brick1/gv0 glusterp3:/bricks/brick1/gv0 glusterp4:/bricks/brick1/gv0
Replica 2 volumes are prone to split-brain. Use Arbiter or Replica 3 to avoid this. See: http://docs.gluster.org/en/latest/Administrator%20Guide/Split%20brain%20and%20ways%20to%20deal%20with%20it/.
Do you still want to continue?
 (y/n) n

Usage:
volume create <NEW-VOLNAME> [stripe <COUNT>] [replica <COUNT> [arbiter <COUNT>]] [disperse [<COUNT>]] [disperse-data <COUNT>] [redundancy <COUNT>] [transport <tcp|rdma|tcp,rdma>] <NEW-BRICK>?<vg_name>... [force]

[root@glustep1 ~]# rpm -q glusterfs
glusterfs-4.0.1-1.el7.x86_64
[root@glustep1 ~]# gluster peer status
Number of Peers: 3

Hostname: glusterp3
Uuid: cb60017a-003c-43d7-b94c-7e44072fad74
State: Peer in Cluster (Connected)

Hostname: glusterp2
Uuid: c869b8cc-fafa-45ca-b189-beb8fa444b3b
State: Peer in Cluster (Connected)

Hostname: glusterp4
Uuid: b6a3927f-be5d-4fb6-af56-d1f5c7412050
State: Peer in Cluster (Connected)
[root@glustep1 ~]# 
========

So this since the user group does not know is either a bug or an error in or unclear documentation.

Version-Release number of selected component (if applicable):
(centos 7.4)
glusterfs-4.0.1-1.el7.x86_64

How reproducible:
everytime

Steps to Reproduce:
Build 4 nodes as per,
https://wiki.centos.org/SpecialInterestGroup/Storage/gluster-Quickstart

1. run command as above in attempting to make a distributed-replicated volume as following documentation,
https://access.redhat.com/documentation/en-US/Red_Hat_Storage/2.1/html/Administration_Guide/sect-User_Guide-Setting_Volumes-Distributed_Replicated.html
"Example 6.5. Four Node Distributed Replicated Volume with a Two-way Replication"

also this document,
https://www.howtoforge.com/distributed-replicated-storage-across-four-storage-nodes-with-glusterfs-3.2.x-on-ubuntu-12.10

also,
https://docs.gluster.org/en/latest/Administrator%20Guide/Setting%20Up%20Volumes/
 
2.
3.

Actual results:

message as above

Expected results:
gv0 is made.

Additional info:
Comment 1 gzcwnk 2018-04-18 22:32:06 UTC 
Fully patched & no difference.
Comment 2 Shyamsundar 2018-06-20 18:29:23 UTC 
This bug reported is against a version of Gluster that is no longer maintained
(or has been EOL'd). See https://www.gluster.org/release-schedule/ for the
versions currently maintained.

As a result this bug is being closed.

If the bug persists on a maintained version of gluster or against the mainline
gluster repository, request that it be reopened and the Version field be marked
appropriately.