Bug 1278325
Summary: | DHT: Once remove brick start failed in between Remove brick commit should not be allowed | |||
---|---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Sakshi <sabansal> | |
Component: | distribute | Assignee: | Atin Mukherjee <amukherj> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
Severity: | medium | Docs Contact: | ||
Priority: | medium | |||
Version: | mainline | CC: | amukherj, bugs, mzywusko, sasundar, smohan, spalai, storage-qa-internal | |
Target Milestone: | --- | Keywords: | ZStream | |
Target Release: | --- | |||
Hardware: | All | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.9.0 | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | ||
Clone Of: | 1258875 | |||
: | 1332370 1333237 (view as bug list) | Environment: | ||
Last Closed: | 2017-03-27 18:21:34 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: | 1258875 | |||
Bug Blocks: | 1332370, 1333237 |
Description
Sakshi
2015-11-05 09:32:17 UTC
Patch posted at http://review.gluster.org/#/c/12513/ REVIEW: http://review.gluster.org/12513 (glusterd: remove-brick commit should not be allowed when remove-brick start failed) posted (#2) for review on master by Sakshi Bansal REVIEW: http://review.gluster.org/12513 (glusterd: remove-brick commit should not succeed when migration failed) posted (#3) for review on master by Sakshi Bansal This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions REVIEW: http://review.gluster.org/12513 (glusterd: remove-brick commit should not succeed when migration failed) posted (#4) for review on master by Sakshi Bansal COMMIT: http://review.gluster.org/12513 committed in master by Atin Mukherjee (amukherj) ------ commit 614a048c59d9b22e090acc0f1bdcb8c1be67f97a Author: Sakshi Bansal <sabansal> Date: Thu Nov 5 15:09:31 2015 +0530 glusterd: remove-brick commit should not succeed when migration failed While remove a brick if the data migration was not successful, remove-brick commit should not succeed as this can lead to data loss. Change-Id: I1eac0ef775cc6910ece0e46ebb04051444d54393 BUG: 1278325 Signed-off-by: Sakshi Bansal <sabansal> Reviewed-on: http://review.gluster.org/12513 Smoke: Gluster Build System <jenkins.com> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.com> Reviewed-by: Atin Mukherjee <amukherj> Tested-by: Atin Mukherjee <amukherj> This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.9.0, please open a new bug report. glusterfs-3.9.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/gluster-users/2016-November/029281.html [2] https://www.gluster.org/pipermail/gluster-users/ |