Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1028965 - Dist-geo-rep : geo-rep config shows ignore_deletes as true always, even though its not true.
Dist-geo-rep : geo-rep config shows ignore_deletes as true always, even thoug...
Status: CLOSED ERRATA
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: geo-replication (Show other bugs)
2.1
x86_64 Linux
medium Severity high
: ---
: RHGS 3.1.0
Assigned To: Aravinda VK
storage-qa-internal@redhat.com
config
:
Depends On:
Blocks: 1202842 1223636
  Show dependency treegraph
 
Reported: 2013-11-11 06:20 EST by Vijaykumar Koppad
Modified: 2015-07-29 00:29 EDT (History)
5 users (show)

See Also:
Fixed In Version: glusterfs-3.7.0-2.el6rhs
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-07-29 00:29:47 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:1495 normal SHIPPED_LIVE Important: Red Hat Gluster Storage 3.1 update 2015-07-29 04:26:26 EDT

  None (edit)
Description Vijaykumar Koppad 2013-11-11 06:20:41 EST
Description of problem: geo-rep config shown ignore_deletes: true always, even though it not true for changelog. 

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
[root@vertigo ~]# gluster v geo master 10.70.36.52::slave config ignore_deletes
true

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>


Version-Release number of selected component (if applicable): glusterfs-3.4.0.42rhs-1


How reproducible: Happens everytime. 


Steps to Reproduce:
1.create and start a geo-rep relationship between master and slave.
2.check the config ignore_deletes


Actual results: It will be true always


Expected results: It shouldn't show true always, people might end up deleting files from master and losing data from slave too. 


Additional info:
Comment 2 Vijaykumar Koppad 2014-06-04 04:59:46 EDT
Still in the geo-rep config output, we have ignore_deletes as true even though we don't ignore deletes. This could be disastrous, since sys-admin might delete some data on master assuming that it won't be deleted on slave. Either remove the that entry from config output or change the behavior. 

Version: glusterfs-3.6.0.12-1.el6rhs


>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
# gluster v geo master 10.70.43.170::slave config ignore_deletes
true
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Comment 4 Aravinda VK 2015-02-05 01:20:59 EST
Upstream patch sent for review http://review.gluster.org/#/c/9583/
Comment 9 Rahul Hinduja 2015-05-26 03:37:51 EDT
Verified with the build: glusterfs-3.7.0-2.el6rhs.x86_64

By default the ignore_deletes option is set to false. At this time, the deletes are picked up by changelog crawl and is sync to the slave. If you set the ignore_deletes option is set explicitly to true. The deletes from master are not synced to slave. This is expected and marking the bug as verified.

[root@georep1 scripts]# gluster volume geo-replication master 10.70.46.154::slave config ignore_deletes
false
[root@georep1 scripts]# 
[root@georep1 scripts]# gluster volume geo-replication master 10.70.46.154::slave config ignore_deletes true
geo-replication config updated successfully
[root@georep1 scripts]# gluster volume geo-replication master 10.70.46.154::slave config ignore_deletes
true
[root@georep1 scripts]#
Comment 11 errata-xmlrpc 2015-07-29 00:29:47 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-1495.html

Note You need to log in before you can comment on or make changes to this bug.