Description of problem: Snapshot status command fails with the error "snapname not found" during quorum check. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/7737 (glusterd/snapshot : Quorum check should not be made for snapshot status command.) posted (#1) for review on master by Sachin Pandit (spandit)
REVIEW: http://review.gluster.org/7737 (glusterd/snapshot : Quorum check should not be made if we perform snapshot status command.) posted (#2) for review on master by Sachin Pandit (spandit)
REVIEW: http://review.gluster.org/7737 (glusterd/snapshot : Quorum check should not be made if we perform snapshot status command.) posted (#3) for review on master by Sachin Pandit (spandit)
REVIEW: http://review.gluster.org/7737 (glusterd/snapshot : Quorum check should not be made if we perform snapshot status command.) posted (#4) for review on master by Sachin Pandit (spandit)
COMMIT: http://review.gluster.org/7737 committed in master by Kaushal M (kaushal) ------ commit 7d22fca1f5c9d792b148bae15e8d26a9c5d63efa Author: Sachin Pandit <spandit> Date: Mon May 12 07:54:59 2014 +0530 glusterd/snapshot : Quorum check should not be made if we perform snapshot status command. Problem : Snapshot status command used to fail as it used to hit the quorum check path. Solution : The condition checking where snapname is fetched based on the presence of snap_volume is moved inside create switch case. And also moved the chunk of code which does the actual quorum check to new function to make the code more readable. Change-Id: Idda2d7c576cdfab3a7d087bfa74bfa616372c20e BUG: 1096700 Signed-off-by: Sachin Pandit <spandit> Reviewed-on: http://review.gluster.org/7737 Reviewed-by: Rajesh Joseph <rjoseph> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Raghavendra Bhat <raghavendra> Reviewed-by: Kaushal M <kaushal>
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