Bug 1214912
Summary: | Failure to recover disperse volume after add-brick failure | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | vnosov <vnosov> |
Component: | glusterd | Assignee: | bugs <bugs> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.6.2 | CC: | bugs, vnosov |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-08-01 04:42: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: |
Description
vnosov
2015-04-23 20:21:36 UTC
The problem is with brick that was used for expansion. After command "add-brick" fails some attributes are left on expansion bricks. These attributes do not let use these bricks at "add-brick" command later. The volume itself is OK. Assigning to glusterd based on comment-1 This is not a security bug, not going to fix this in 3.6.x because of http://www.gluster.org/pipermail/gluster-users/2016-July/027682.html If the issue persists in the latest releases, please feel free to clone them |