Bug 1217929

Summary:	ignore_deletes option is not something you can configure
Product:	[Community] GlusterFS	Reporter:	Aravinda VK <avishwan>
Component:	geo-replication	Assignee:	Aravinda VK <avishwan>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	3.7.0	CC:	aavati, avishwan, bugs, csaba, gluster-bugs, jshucart, nlevinki, storage-qa-internal
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.7.0beta2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1189363	Environment:
Last Closed:	2015-05-14 17:27:28 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:	1127401, 1189363
Bug Blocks:	1199352

Description Aravinda VK 2015-05-03 05:04:36 UTC

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

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

Description of problem:

When I try to set ignore-deletes on geo-replication, it tells me it is a "Reserved option".  This should not be the easy, right?

--- Additional comment from Anand Avati on 2015-02-05 01:14:34 EST ---

REVIEW: http://review.gluster.org/9583 (geo-rep: Re Enable ignore_deletes Option) posted (#1) for review on master by Aravinda VK (avishwan)

--- Additional comment from Anand Avati on 2015-03-26 14:21:34 EDT ---

REVIEW: http://review.gluster.org/9583 (geo-rep: Re Enable ignore_deletes Option) posted (#2) for review on master by Aravinda VK (avishwan)

--- Additional comment from Anand Avati on 2015-04-27 07:39:04 EDT ---

COMMIT: http://review.gluster.org/9583 committed in master by Vijay Bellur (vbellur) 
------
commit 5dd40bd4ad768c4d2eb07520efeb49467c709df6
Author: Aravinda VK <avishwan>
Date:   Wed Feb 4 23:08:31 2015 +0530

    geo-rep: Re Enable ignore_deletes Option
    
    If this option is set, Deletes will not be propogated to Slave.
    This option is applicable for UNLINK and RMDIR.
    
    gluster volume geo-replication <MASTER> <SLAVEHOST>::<SLAVEVOL> \
            config ignore_deletes true
    
    Default value is false.
    
    PS: Use this option with caution, If you create the file in master
    with same path then it fails to sync to slave. Old file in Slave
    will have different GFID compared to New.
    
    BUG: 1189363
    Change-Id: I1f7816d1ea36460a654873739d3fb1b6c13e0f8d
    Signed-off-by: Aravinda VK <avishwan>
    Reviewed-on: http://review.gluster.org/9583
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Kotresh HR <khiremat>

Comment 1 Anand Avati 2015-05-03 05:05:30 UTC

REVIEW: http://review.gluster.org/10498 (geo-rep: Re Enable ignore_deletes Option) posted (#1) for review on release-3.7 by Aravinda VK (avishwan)

Comment 2 Anand Avati 2015-05-03 18:10:46 UTC

COMMIT: http://review.gluster.org/10498 committed in release-3.7 by Vijay Bellur (vbellur) 
------
commit e4e8c378728da595d18d488b438662efc2fea844
Author: Aravinda VK <avishwan>
Date:   Wed Feb 4 23:08:31 2015 +0530

    geo-rep: Re Enable ignore_deletes Option
    
    If this option is set, Deletes will not be propogated to Slave.
    This option is applicable for UNLINK and RMDIR.
    
    gluster volume geo-replication <MASTER> <SLAVEHOST>::<SLAVEVOL> \
            config ignore_deletes true
    
    Default value is false.
    
    PS: Use this option with caution, If you create the file in master
    with same path then it fails to sync to slave. Old file in Slave
    will have different GFID compared to New.
    
    BUG: 1217929
    Change-Id: I1f7816d1ea36460a654873739d3fb1b6c13e0f8d
    Signed-off-by: Aravinda VK <avishwan>
    Reviewed-on: http://review.gluster.org/9583
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Kotresh HR <khiremat>
    Reviewed-on: http://review.gluster.org/10498
    Tested-by: NetBSD Build System

Comment 3 Niels de Vos 2015-05-14 17:27:28 UTC

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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 4 Niels de Vos 2015-05-14 17:28:49 UTC

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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 5 Niels de Vos 2015-05-14 17:35:20 UTC

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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user