Bug 1763134

Summary: clearly state that replica 2 is deprecated in cli warning when user tries to create replica 2 volume
Product: [Community] GlusterFS Reporter: Sanju <srakonde>
Component: cliAssignee: Sanju <srakonde>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: urgent    
Version: mainlineCC: bugs, nchilaka, rhinduja, rhs-bugs, storage-qa-internal
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1763124 Environment:
Last Closed: 2019-11-19 10:14:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1763124    
Bug Blocks:    

Description Sanju 2019-10-18 10:20:05 UTC
Description of problem:
======================
as per admin guide of 3.4 in section 5.6.1( https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.4/html-single/administration_guide/index#sect-Creating_Replicated_Volumes ) we clearly state that creation of new x2 replica volumes stands deprecated.

We must hence change the warning in CLI to reflect the same.


currently we are getting below warning:

[root@dhcp35-190 ~]# gluster v create rep rep 2 dhcp35-237.lab.eng.blr.redhat.com:/gluster/brick1/rep2 $HOSTNAME:/gluster/brick1/rep2
Replica 2 volumes are prone to split-brain. Use Arbiter or Replica 3 to avoid this.
Do you still want to continue?
 (y/n) 



Need to change it to something like below:
*CREATION OF A NEW REPLICA 2 VOLUME STANDS DEPRECATED*  as they are prone to split-brain. Use Arbiter or Replica 3 to avoid this.

Do you still want to continue ?
 (y/n)

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

Comment 1 Worker Ant 2019-10-18 10:28:00 UTC
REVIEW: https://review.gluster.org/23565 (cli: change the warning message) posted (#1) for review on master by Sanju Rakonde

Comment 2 Sanju 2019-11-19 10:14:13 UTC
Closing this bug as we don't need it at upstream.