Bug 1330484

Summary:	remove-brick commit is happening when rebalance failed.
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Byreddy <bsrirama>
Component:	distribute	Assignee:	Bug Updates Notification Mailing List <rhs-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	storage-qa-internal <storage-qa-internal>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.1	CC:	sabansal
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-02 15:09:18 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 Byreddy 2016-04-26 10:30:18 UTC

Description of problem:
=======================
remove-brick commit is happening when rebalance failed due to one of volume brick down.


Version-Release number of selected component (if applicable):
=============================================================
glusterfs-3.7.9-2.el7


How reproducible:
=================
Always


Steps to Reproduce:
===================
1. Have two node cluster with distribute volume (3 bricks)
2. FUSE mount and write enough data 
3. bring down one of brick //kill -9 brick_pid
4. remove one active brick (remove-brick start)
5. Check remove-brick status // you will see rebalance failure
6. Try to do remove-brick commit //will get committed and you will lose the data.

Actual results:
===============
Remove-brick commit is happening without rebalance success


Expected results:
=================
remove-brick commit should not happen if rebalance failed.

Additional info:

Comment 3 Sakshi 2016-05-02 15:09:18 UTC


*** This bug has been marked as a duplicate of bug 1258875 ***