Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 950048

Summary:	[RHEV-RHS]: "gluster volume sync" command not working as expected
Product:	[Community] GlusterFS	Reporter:	Jeff Darcy <jdarcy>
Component:	glusterd	Assignee:	krishnan parthasarathi <kparthas>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	3.4.0-beta	CC:	amarts, gluster-bugs, grajaiya, joe, nsathyan, rhs-bugs, shaines, spandura, vbellur
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.4.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	865700	Environment:
Last Closed:	2013-07-24 17:14:47 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:
Bug Depends On:
Bug Blocks:	865700, 918917

Description Jeff Darcy 2013-04-09 14:23:19 UTC

+++ This bug was initially created as a clone of Bug #865700 +++

Description of problem:
------------------------
"gluster volume sync <hostname> <volume_name>" doesn't sync the volume information to the hosts in peer. 

For all the sync command options the output is always "please delete all the volume before full sync" . Deleting all volumes is not ideal at all. 

[10/12/12 - 13:02:19 root@rhs-client6 ~]# gluster volume sync client-6 
please delete all the volumes before full sync

[10/12/12 - 13:02:42 root@rhs-client6 ~]# gluster volume sync client-6 all
please delete all the volumes before full sync

[10/12/12 - 13:02:44 root@rhs-client6 ~]# gluster volume sync client-6 replicate-rhevh
please delete the volume: replicate-rhevh before sync


Version-Release number of selected component (if applicable):
-------------------------------------------------------------
[10/12/12 - 13:17:17 root@rhs-client6 ~]# rpm -qa | grep gluster
glusterfs-geo-replication-3.3.0rhsvirt1-7.el6rhs.x86_64
vdsm-gluster-4.9.6-14.el6rhs.noarch
gluster-swift-plugin-1.0-5.noarch
gluster-swift-container-1.4.8-4.el6.noarch
org.apache.hadoop.fs.glusterfs-glusterfs-0.20.2_0.2-1.noarch
glusterfs-3.3.0rhsvirt1-7.el6rhs.x86_64
glusterfs-server-3.3.0rhsvirt1-7.el6rhs.x86_64
glusterfs-rdma-3.3.0rhsvirt1-7.el6rhs.x86_64
gluster-swift-proxy-1.4.8-4.el6.noarch
gluster-swift-account-1.4.8-4.el6.noarch
gluster-swift-doc-1.4.8-4.el6.noarch
glusterfs-fuse-3.3.0rhsvirt1-7.el6rhs.x86_64
glusterfs-debuginfo-3.3.0rhsvirt1-7.el6rhs.x86_64
gluster-swift-1.4.8-4.el6.noarch
gluster-swift-object-1.4.8-4.el6.noarch


[10/12/12 - 13:17:24 root@rhs-client6 ~]# gluster --version
glusterfs 3.3.0rhsvirt1 built on Oct  8 2012 15:23:00


How reproducible:
----------------
Often

Additional Info:-
----------------
Refer to Bug865693 . The bug 865693 needs volume sync and we are unable to perform sync operation.

--- Additional comment from RHEL Product and Program Management on 2012-10-12 03:55:06 EDT ---

Since this issue was entered in bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

--- Additional comment from Amar Tumballi on 2012-10-15 03:43:25 EDT ---

this is a behavior of glusterd in general, and not very specific to 2.0+ related testing alone.

--- Additional comment from krishnan parthasarathi on 2012-11-15 01:22:45 EST ---

Submitted patch at http://review.gluster.org/4188

--- Additional comment from Amar Tumballi on 2012-11-27 22:07:22 EST ---

keeping it in POST for indicating that the patch is in review process.

--- Additional comment from Vijay Bellur on 2012-11-28 02:28:12 EST ---

CHANGE: http://review.gluster.org/4188 (glusterd: volume-sync shouldn't validate volume-id) merged in master by Vijay Bellur (vbellur)

--- Additional comment from krishnan parthasarathi on 2013-02-27 04:35:27 EST ---

The issue is still seen. This has come about since the following commit - http://review.gluster.com/4570.

--- Additional comment from Vijay Bellur on 2013-03-11 00:02:26 EDT ---

CHANGE: http://review.gluster.org/4624 (glusterd: Fixed volume-sync in synctask codepath.) merged in master by Vijay Bellur (vbellur)

Comment 1 Anand Avati 2013-04-12 07:17:56 UTC

REVIEW: http://review.gluster.org/4643 (glusterd: Fixed volume-sync in synctask codepath.) posted (#4) for review on release-3.4 by Krishnan Parthasarathi (kparthas)

Comment 2 Anand Avati 2013-04-12 11:07:38 UTC

REVIEW: http://review.gluster.org/4815 (glusterd: volume-sync needs to work with rejected peers) posted (#1) for review on master by Krishnan Parthasarathi (kparthas)

Comment 3 Anand Avati 2013-04-12 11:10:02 UTC

REVIEW: http://review.gluster.org/4643 (glusterd: Fixed volume-sync in synctask codepath.) posted (#6) for review on release-3.4 by Krishnan Parthasarathi (kparthas)

Comment 4 Anand Avati 2013-04-12 12:59:32 UTC

COMMIT: http://review.gluster.org/4643 committed in release-3.4 by Vijay Bellur (vbellur) 
------
commit c88fa6d979900e7ee32bd13445bcf4a1dcf3f617
Author: Krishnan Parthasarathi <kparthas>
Date:   Tue Mar 5 14:11:02 2013 +0530

    glusterd: Fixed volume-sync in synctask codepath.
    
    Change-Id: I2911d3ac80825310f84c5ba6bd7890e65e1ee219
    BUG: 950048
    Signed-off-by: Krishnan Parthasarathi <kparthas>
    Reviewed-on: http://review.gluster.org/4643
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Vijay Bellur <vbellur>

Comment 5 Anand Avati 2013-04-22 18:13:41 UTC

COMMIT: http://review.gluster.org/4815 committed in master by Vijay Bellur (vbellur) 
------
commit 3f22b5bb7069cfff8607320c262702418c731c89
Author: Krishnan Parthasarathi <kparthas>
Date:   Fri Apr 12 16:35:51 2013 +0530

    glusterd: volume-sync needs to work with rejected peers
    
    Change-Id: I970a51d3f62bcf414eb9552a68d1068430b93216
    BUG: 950048
    Signed-off-by: Krishnan Parthasarathi <kparthas>
    Reviewed-on: http://review.gluster.org/4815
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Vijay Bellur <vbellur>

Comment 6 Niels de Vos 2014-10-21 13:48:56 UTC

*** Bug 765401 has been marked as a duplicate of this bug. ***