Bug 1212701
| Summary: | Remove replace-brick with data migration support from gluster cli | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Gaurav Kumar Garg <ggarg> |
| Component: | glusterd | Assignee: | Gaurav Kumar Garg <ggarg> |
| Status: | CLOSED ERRATA | QA Contact: | SATHEESARAN <sasundar> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | rhgs-3.0 | CC: | amukherj, bmohanra, ggarg, nlevinki, nsathyan, rcyriac, sasundar, smohan, vagarwal, vbellur |
| Target Milestone: | --- | ||
| Target Release: | RHGS 3.1.0 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | glusterfs-3.7.0-2.el6rhs | Doc Type: | Bug Fix |
| Doc Text: |
Previously, there was a data loss issue during replace brick operation. In this release, replace-brick operation with data migration support has been deprecated from Gluster. With this fix, replace brick command will support only one commad
gluster volume replace-brick <VOLNAME> <SOURCE-BRICK> <NEW-BRICK> {commit force}
|
Story Points: | --- |
| Clone Of: | 1074429 | Environment: | |
| Last Closed: | 2015-07-29 04:41:08 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: | 1074429 | ||
| Bug Blocks: | 1074415, 1094119, 1202842, 1218602, 1255645 | ||
|
Comment 2
SATHEESARAN
2015-04-17 13:54:52 UTC
(In reply to SATHEESARAN from comment #2) > Vivek, > > This bug was earlier marked for RH-Gluster Storage 3.1 > I see that you have removed the RHS 3.1 tracker from this bug. > Any reasons ? This is not a sure target for RHS 3.1.0. Still waiting on Gaurav. upstream patch url: http://review.gluster.org/#/c/10577/ confirmed that all the replace-brick commands except {commit force} was removed
with glusterfs-3.7.0-2.el6rhs ( RHGS 3.1 nightly build )
Marking this bug as VERIFIED
Hi Gaurav, The doc text is updated. Please review the same and share your technical review comments. If it looks ok, then sign-off on the same. Regards, Bhavana 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. https://rhn.redhat.com/errata/RHSA-2015-1495.html hi, this doc text looks good to me. |