Bug 805802 - Replace-brick operations just exits with operation failed.
Summary: Replace-brick operations just exits with operation failed.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: cli
Version: mainline
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Amar Tumballi
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 817967
TreeView+ depends on / blocked
 
Reported: 2012-03-22 07:57 UTC by Vijaykumar Koppad
Modified: 2014-08-25 00:49 UTC (History)
3 users (show)

Fixed In Version: glusterfs-3.4.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-24 17:25:44 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

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)
Note You need to log in before you can comment on or make changes to this bug.