[Bugs] [Bug 1340853] [geo-rep]: If the session is renamed, geo-rep configuration are not retained

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1340853

Kotresh HR <khiremat at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |POST
                 CC|                            |khiremat at redhat.com



--- Comment #3 from Kotresh HR <khiremat at redhat.com> ---
Description of problem:
=======================

With the recent changes, we support to rename the existing geo-rep session from
one slave host to another slave host. Expected is to rename only the session
and retain all the configuration/status as of the previous session. 

But the older configurations are not retained which passively breaks the
geo-rep functionality for this use case. 

Existing session between: baloo 10.70.37.88::bagheera

[root at dhcp37-162 ~]# gluster volume geo-replication baloo 10.70.37.88::bagheera
config change_detector
xsync
[root at dhcp37-162 ~]# gluster volume geo-replication baloo 10.70.37.88::bagheera
config ignore_deletes
true
[root at dhcp37-162 ~]# gluster volume geo-replication baloo 10.70.37.88::bagheera
config use_meta_volume
true
[root at dhcp37-162 ~]#

New Session between: baloo 10.70.37.43::bagheera 

[root at dhcp37-162 ~]# gluster volume geo-replication baloo 10.70.37.43::bagheera
config use_meta_volume
[root at dhcp37-162 ~]# gluster volume geo-replication baloo 10.70.37.43::bagheera
config ignore_deletes
false
[root at dhcp37-162 ~]# gluster volume geo-replication baloo 10.70.37.43::bagheera
config change_detector
changelog
[root at dhcp37-162 ~]# 



Version-Release number of selected component (if applicable):
=============================================================


How reproducible:
=================

Always


Steps to Reproduce:
===================
1. Create georep session between master, slavehost1 and slave
2. Update configs for this session
3. Stop existing session
4. Recreate session between master, slavehost2 and slave
5. Start the session
6. Verify for the configs setup at step 2

Actual results:
===============

Config options are reset


Expected results:
=================

Since it is a rename of a session and not the new session, all config options
should be retained

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=u08ZjWWsm0&a=cc_unsubscribe