Bug 805802

Summary:	Replace-brick operations just exits with operation failed.
Product:	[Community] GlusterFS	Reporter:	Vijaykumar Koppad <vkoppad>
Component:	cli	Assignee:	Amar Tumballi <amarts>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bbandari, gluster-bugs, vraman
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.4.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-07-24 17:25:44 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:
Bug Blocks:	817967

Description Vijaykumar Koppad 2012-03-22 07:57:21 UTC

Description of problem:
After adding bricks to a volume, with relace-brick operation, it exits with operation failed.

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


How reproducible:Always


Steps to Reproduce:
1.Create and start a volume 
2.Add-brick to that volume 
3.Then perform any replace-brick operation.

Comment 1 Anand Avati 2012-03-22 11:19:25 UTC

CHANGE: http://review.gluster.com/3000 (glusterd: fix bugs of syncop for operations) merged in master by Vijay Bellur (vijay)

Comment 2 Anand Avati 2012-03-22 11:30:43 UTC

CHANGE: http://review.gluster.com/3002 (glusterd: bring back the 'non-synctask' behavior) merged in master by Vijay Bellur (vijay)