+++ This bug was initially created as a clone of Bug #1240196 +++ Description of problem: Unable to pause georep session if one of the nodes in cluster is not part of master volume. Version-Release number of selected component (if applicable): mainline How reproducible: Always Steps to Reproduce: 1. Add 3 nodes in the cluster. 2. Create a master volume with 2 nodes. 3. Create a geo rep session. 4. Try to Pause the geo rep session. Actual results: Unable to pause georep session Expected results: georep session should be paused successfully Additional info: [2015-07-06 05:31:23.751865] E [glusterd-op-sm.c:254:glusterd_get_txn_opinfo] (--> 0-management: Unable to get transaction opinfo for transaction ID : d6d23c5d-efe1-4c48-b7b1-6a43e9f6a622 [2015-07-06 05:31:25.066529] I [MSGID: 106327] [glusterd-geo-rep.c:2180:glusterd_get_statefile_name] 0-management: Using passed config template(/var/lib/glusterd/geo-replication/vol1_10.70.46.129_vol1_slave1/gsyncd.conf). [2015-07-06 05:31:25.408344] E [MSGID: 106308] [glusterd-geo-rep.c:1840:glusterd_op_verify_gsync_running] 0-management: geo-replication session b/w vol1 & 10.70.46.129::vol1_slave1 is not running on this node. [2015-07-06 05:31:25.408464] E [MSGID: 106301] [glusterd-op-sm.c:5088:glusterd_op_ac_stage_op] 0-management: Stage failed on operation 'Volume Geo-replication', Status : -1
REVIEW: http://review.gluster.org/11549 (glusterd/geo-rep: Fix failure of geo-rep pause) posted (#1) for review on master by Kotresh HR (khiremat)
COMMIT: http://review.gluster.org/11549 committed in master by Krishnan Parthasarathi (kparthas) ------ commit 91e1d0dd620941c91794d697a8388cd524d2e3bf Author: Kotresh HR <khiremat> Date: Mon Jul 6 15:05:43 2015 +0530 glusterd/geo-rep: Fix failure of geo-rep pause Geo-replication pause fails if one or more of the nodes in the master cluster is not part of master volume. If the master volume bricks are not part of the node, it should be ignored. The check is added to fix the issue. Change-Id: Iba57d66b6db6919f42a95dd66e6db9ad1b21503b BUG: 1240229 Signed-off-by: Kotresh HR <khiremat> Reviewed-on: http://review.gluster.org/11549 Tested-by: NetBSD Build System <jenkins.org> Reviewed-by: Avra Sengupta <asengupt> Reviewed-by: Krishnan Parthasarathi <kparthas>
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.
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.8.0, please open a new bug report. glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user