REVIEW: http://review.gluster.org/8158 (glusterd/snapshot : Fixing Msging in glusterd_mgmt_v3_initiate_snap_phases) posted (#1) for review on master by Joseph Fernandes (josferna)
REVIEW: http://review.gluster.org/8158 (glusterd/snapshot: Fixed errmsg and Quorum check in Snapshot Operation) posted (#2) for review on master by Joseph Fernandes (josferna)
REVIEW: http://review.gluster.org/8158 (glusterd/snapshot: Fixed errmsg and Quorum check in Snapshot Operation) posted (#3) for review on master by Joseph Fernandes (josferna)
REVIEW: http://review.gluster.org/8158 (glusterd/snapshot: Fixed errmsg and Quorum check in Snapshot Operation) posted (#4) for review on master by Joseph Fernandes (josferna)
REVIEW: http://review.gluster.org/8158 (glusterd/snapshot: Fixed errmsg and Quorum check in Snapshot Operation) posted (#5) for review on master by Joseph Fernandes (josferna)
REVIEW: http://review.gluster.org/8158 (glusterd/snapshot: Fixed errmsg and Quorum check in Snapshot Operation) posted (#6) for review on master by Joseph Fernandes (josferna)
COMMIT: http://review.gluster.org/8158 committed in master by Krishnan Parthasarathi (kparthas) ------ commit a9797607a968a4d54d1f28f44048ec5925721098 Author: Joseph Fernandes <josferna> Date: Tue Jun 24 14:19:29 2014 +0530 glusterd/snapshot: Fixed errmsg and Quorum check in Snapshot Operation 1) Removing the static message "unbarrier brick opfailed" and log errors / message in places. 2) Calling the Snapshot Volume Quorum check if the commit is passed, as the check(which checks the sanity of glusterds or snapvolume) a successful commit makes more sense. Change-Id: I7b8f77aa9b2e553893a6ae71bd4b5bbbb60ab8f1 BUG: 1112559 Signed-off-by: Joseph Fernandes <josferna> Reviewed-on: http://review.gluster.org/8158 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Atin Mukherjee <amukherj> Reviewed-by: Avra Sengupta <asengupt> Reviewed-by: Krishnan Parthasarathi <kparthas> Tested-by: Krishnan Parthasarathi <kparthas>
REVIEW: http://review.gluster.org/8259 (glusterd/regression: Increase time for to chk snpsht brick status) posted (#1) for review on master by Joseph Fernandes (josferna)
REVIEW: http://review.gluster.org/8259 (glusterd/regression: Increase time for to chk snpsht brick status) posted (#2) for review on master by Joseph Fernandes (josferna)
REVIEW: http://review.gluster.org/8259 (glusterd/regression: Increase time for to chk snpsht brick status) posted (#3) for review on master by Joseph Fernandes (josferna)
REVIEW: http://review.gluster.org/8259 (glusterd/regression: Temp fix for spurious err) posted (#4) for review on master by Joseph Fernandes (josferna)
REVIEW: http://review.gluster.org/8259 (glusterd/regression: Temp fix for spurious err) posted (#5) for review on master by Joseph Fernandes (josferna)
COMMIT: http://review.gluster.org/8259 committed in master by Vijay Bellur (vbellur) ------ commit c7251ebfe8e14090f9420786973c5f8232555b8e Author: Joseph Fernandes <josferna> Date: Tue Jul 8 13:06:04 2014 +0530 glusterd/regression: Temp fix for spurious err As discussed in the mail, Disabling the checking of snap brick status until the investigation is done on the port bind issue. Change-Id: I8854cee050de1b7f843e3d40631b6cb61fd8583e BUG: 1112559 Signed-off-by: Joseph Fernandes <josferna> Reviewed-on: http://review.gluster.org/8259 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijay Bellur <vbellur>
REVIEW: http://review.gluster.org/8295 (Testing the regression test: Please dont review this!!) posted (#1) for review on master by Joseph Fernandes (josferna)
REVIEW: http://review.gluster.org/8295 (Testing the regression test: Please dont review this!!) posted (#2) for review on master by Joseph Fernandes (josferna)
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED. Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution. [1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html [2] http://supercolony.gluster.org/pipermail/gluster-users/
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.6.1, please reopen this bug report. glusterfs-3.6.1 has been announced [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://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html [2] http://supercolony.gluster.org/mailman/listinfo/gluster-users