Bug 889999 - Replace-brick start fails on the non-originator node.
Summary: Replace-brick start fails on the non-originator node.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: krishnan parthasarathi
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-24 10:08 UTC by krishnan parthasarathi
Modified: 2015-11-03 23:05 UTC (History)
4 users (show)

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

Attachments (Terms of Use)

Description krishnan parthasarathi 2012-12-24 10:08:13 UTC 
Description of problem:
replace-brick fails on remote node saying "Failed to get op ctx".


Version-Release number of selected component (if applicable):
commit on upstream/master: 91cc423b48df800dcfff7040ca4a95ef2a9d6afc

How reproducible:
1/1

Steps to Reproduce:
1. Create a volume
2. Probe a peer
3. Perform replace-brick where src-brick and dst-brick are on different nodes.
  
Actual results:
replace-brick fails to start.

Expected results:
replace-brick should succeed.

Additional info:
We notice critical log level message - "Failed to get op ctx" in the glusterd log file.
Comment 1 Amar Tumballi 2012-12-24 10:48:20 UTC 
http://review.gluster.org/4352
Comment 2 Vijay Bellur 2013-01-09 07:39:47 UTC 
CHANGE: http://review.gluster.org/4352 (glusterd: Set replace-brick id in op ctx only in origin glusterd) merged in master by Vijay Bellur (vbellur)
Note You need to log in before you can comment on or make changes to this bug.