Description of problem: While performing an in-service upgrade from 3.4.4 to 3.5.0(glusterfs-6.0-17) 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-17 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. Additional info:
Upstream fix : https://review.gluster.org/#/c/glusterfs/+/23555/
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://access.redhat.com/errata/RHEA-2019:3249