Bug 763850 (GLUSTER-2118)
Summary: | [3.1.1qa5] : gluster volume sync doesn't start already started volumes | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Harshavardhana <fharshav> |
Component: | cli | Assignee: | krishnan parthasarathi <kparthas> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 3.1.1 | CC: | amarts, cww, gluster-bugs, nsathyan, pkarampu |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.4.0 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-07-24 17:37:24 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Harshavardhana
2010-11-16 18:09:10 UTC
Taking this task after 3.1.3 release, hence this should be present mostly in 3.2.x (or 3.1.3+ releases). We found that glusterd store version is not updated for some of the operations like set, reset, start, stop. In remodeling glusterd store for fix to bug 763486, we fixed this. With this fix this problem should happen only when any operation is performed on volume with same name on *BOTH* peer1, peer2 when they are not connected to each other. |