Bug 1762220 - [geo-rep] sync_method showing rsync instead of tarssh post in-service upgrade
Summary: [geo-rep] sync_method showing rsync instead of tarssh post in-service upgrade
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1763028 1764028
TreeView+ depends on / blocked
 
Reported: 2019-10-16 09:01 UTC by Kotresh HR
Modified: 2019-10-22 07:42 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1763028 1764028 (view as bug list)
Environment:
Last Closed: 2019-10-17 04:04:41 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 23555 0 None Merged geo-rep: Fix config upgrade on non-participating node 2019-10-17 04:04:40 UTC

Comment 1 Worker Ant 2019-10-16 09:04:32 UTC 
REVIEW: https://review.gluster.org/23555 (geo-rep: Fix config upgrade on non-participating node) posted (#1) for review on master by Kotresh HR
Comment 2 Kotresh HR 2019-10-16 11:20:58 UTC 
Description of problem:
While performing an in-service upgrade from 5.x to 6.0 on a non-root geo-rep setup with one volume of each type and use_tarssh set to enabled. It was observed that for a 1x3 replica volume the sync_method was showing rsync instead of tarssh. 

Before upgrade:

[root@dhcp43-49 ~]# gluster v geo-rep masterarb geoaccount.43.153::slavearb config use_tarssh; gluster v geo-rep mastertdisp geoaccount.43.153::slavetdisp config use_tarssh;gluster v geo-rep mastertdistdisp geoaccount.43.153::slavetdistdisp config use_tarssh; gluster v geo-rep masterrep geoaccount.43.153::slaverep config use_tarssh;gluster v geo-rep masterdistrep geoaccount.43.153::slavedistrep config use_tarssh
true
true
true
true
true

After upgrade:

[root@dhcp43-49 ~]# gluster v geo-rep masterarb geoaccount.43.153::slavearb config sync_method; gluster v geo-rep mastertdisp geoaccount.43.153::slavetdisp config sync_method;gluster v geo-rep mastertdistdisp geoaccount.43.153::slavetdistdisp config sync_method; gluster v geo-rep masterrep geoaccount.43.153::slaverep config sync_method;gluster v geo-rep masterdistrep geoaccount.43.153::slavedistrep config sync_method
tarssh
tarssh
tarssh
rsync
tarssh

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

How reproducible:
1/1

Steps to Reproduce:
1.Created a non-root geo-rep setup.
2.Set use_tarssh to true.
3.Performed an in-service upgrade to 3.5.0.
4.Checked the sync method.

Actual results:
sync_method was showing rsync.

Expected results:
sync_method should show tarssh.
Comment 3 Worker Ant 2019-10-17 04:04:41 UTC 
REVIEW: https://review.gluster.org/23555 (geo-rep: Fix config upgrade on non-participating node) merged (#5) on master by Amar Tumballi
Note You need to log in before you can comment on or make changes to this bug.