Bug 878872
Summary: | cannot replace brick in distributed replicated volume | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Vidya Sakar <vinaraya> |
Component: | glusterd | Assignee: | krishnan parthasarathi <kparthas> |
Status: | CLOSED ERRATA | QA Contact: | shylesh <shmohan> |
Severity: | unspecified | Docs Contact: | |
Priority: | high | ||
Version: | 2.0 | CC: | amarts, gluster-bugs, nsathyan, rfortier, rhs-bugs, ricor.bz, shaines, vbellur |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.4.0qa6 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | 875412 | Environment: | |
Last Closed: | 2013-09-23 22:39:20 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: | 875412, 877522 | ||
Bug Blocks: |
Description
Vidya Sakar
2012-11-21 12:56:58 UTC
This bug is fixed with master, for flag (pm-rhel: rhs‑2.1.0+) by bug 877522. not there in 2.0.z branch yet. I tried recreating the issue as follows, 1) Created a volume with 2 bricks in a single node. 2) Added another node to the cluster. 3) Performed replace-brick on the volume such that one of the bricks from the first peer was replaced with another brick, with the same path, to the second peer. 4) Replace-brick returned successfully. I would recommend verification of this on the latest build of rhs-2.0z that is available. Per 03/05 email exchange w/ PM, targeting for Arches. Per 04-10-2013 Storage bug triage meeting, targeting for Big Bend. Verified on 3.4.0.12rhs.beta3-1.el6rhs.x86_64 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1262.html Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1262.html |