Bug 1460993

Summary:	Revert CLI restrictions on running rebalance in VM store use case
Product:	[Community] GlusterFS	Reporter:	Krutika Dhananjay <kdhananj>
Component:	distribute	Assignee:	Krutika Dhananjay <kdhananj>
Status:	CLOSED EOL	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.10	CC:	amukherj, bugs
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1460585	Environment:
Last Closed:	2018-06-20 18:26:59 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:
Bug Depends On:	1460585, 1460997
Bug Blocks:	1457558

Description Krutika Dhananjay 2017-06-13 10:22:00 UTC

+++ This bug was initially created as a clone of Bug #1460585 +++

Description of problem:

Now that some of the users have confirmed rebalance works fine in VM store environments when parallel IO is going on, and sas has also confirmed the same, time to revert the CLI restrictions wrt running rebalance on sharded volumes.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from Worker Ant on 2017-06-12 02:34:33 EDT ---

REVIEW: https://review.gluster.org/17506 (Revert "glusterd: disallow rebalance & remove-brick on a sharded volume") posted (#1) for review on master by Krutika Dhananjay (kdhananj)

--- Additional comment from Worker Ant on 2017-06-13 04:51:48 EDT ---

COMMIT: https://review.gluster.org/17506 committed in master by Atin Mukherjee (amukherj) 
------
commit c0d4081cf4b90a4316b786cc53263a7c56fdb344
Author: Krutika Dhananjay <kdhananj>
Date:   Mon Jun 12 11:17:01 2017 +0530

    Revert "glusterd: disallow rebalance & remove-brick on a sharded volume"
    
    This reverts commit 8375b3d70d5c6268c6770b42a18b2e1bc09e411e.
    
    Now that some of the users have confirmed rebalance works fine without
    causing corruption of VMs, time to revert the CLI restriction.
    
    Change-Id: I45493fcbb1f25fd0fff27b2b3526c42642ccb464
    BUG: 1460585
    Signed-off-by: Krutika Dhananjay <kdhananj>
    Reviewed-on: https://review.gluster.org/17506
    Reviewed-by: Atin Mukherjee <amukherj>
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Reviewed-by: Raghavendra G <rgowdapp>
    CentOS-regression: Gluster Build System <jenkins.org>

Comment 1 Worker Ant 2017-06-13 10:24:45 UTC

REVIEW: https://review.gluster.org/17532 (Revert "glusterd: disallow rebalance & remove-brick on a sharded volume") posted (#1) for review on release-3.10 by Krutika Dhananjay (kdhananj)

Comment 2 Worker Ant 2017-06-20 04:54:25 UTC

COMMIT: https://review.gluster.org/17532 committed in release-3.10 by Raghavendra Talur (rtalur) 
------
commit abaf577626650edb4b9dfdddd43ba04a2a8e8ef3
Author: Krutika Dhananjay <kdhananj>
Date:   Mon Jun 12 11:17:01 2017 +0530

    Revert "glusterd: disallow rebalance & remove-brick on a sharded volume"
    
    This reverts commit 8375b3d70d5c6268c6770b42a18b2e1bc09e411e.
    
    Backport of:
    > Change-Id: I45493fcbb1f25fd0fff27b2b3526c42642ccb464
    > BUG: 1460585
    > Reviewed-on: https://review.gluster.org/17506
    > (cherry-picked from c0d4081cf4b90a4316b786cc53263a7c56fdb344)
    
    Now that some of the users have confirmed rebalance works fine without
    causing corruption of VMs, time to revert the CLI restriction.
    
    Change-Id: I45493fcbb1f25fd0fff27b2b3526c42642ccb464
    BUG: 1460993
    Signed-off-by: Krutika Dhananjay <kdhananj>
    Reviewed-on: https://review.gluster.org/17532
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Atin Mukherjee <amukherj>

Comment 3 Shyamsundar 2018-06-20 18:26:59 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.

Comment 4 Shyamsundar 2018-06-20 18:27:39 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.