Description of problem: geo-rep config CLI takes even the garbage value and succeeds. Version-Release number of selected component (if applicable): glusterfs-3.4.0.43rhs-1.el6rhs.x86_64 How reproducible: Always Steps to Reproduce: 1. gluster v geo master slave_url config use-tarssh blah Actual results: [root@harrier ~]# gluster v geo master falcon::slave config use-tarssh true geo-replication config updated successfully [root@harrier ~]# gluster v geo master falcon::slave config | grep tar use_tarssh: true ssh_command_tar: ssh -oPasswordAuthentication=no -oStrictHostKeyChecking=no -i /var/lib/glusterd/geo-replication/tar_ssh.pem [root@harrier ~]# gluster v geo master falcon::slave config use-tarssh blah geo-replication config updated successfully [root@harrier ~]# gluster v geo master falcon::slave config | grep tar use_tarssh: blah ssh_command_tar: ssh -oPasswordAuthentication=no -oStrictHostKeyChecking=no -i /var/lib/glusterd/geo-replication/tar_ssh.pem [root@harrier ~]# gluster v geo master falcon::slave config use-tarssh dontusetarssh geo-replication config updated successfully [root@harrier ~]# gluster v geo master falcon::slave config | grep tar use_tarssh: dontusetarssh ssh_command_tar: ssh -oPasswordAuthentication=no -oStrictHostKeyChecking=no -i /var/lib/glusterd/geo-replication/tar_ssh.pem Expected results: use-tarssh should take only true, on or some other valid and allowed values. Additional info:
Fixed with https://code.engineering.redhat.com/gerrit/15619
With Invalid values [root@pythagoras ]# gluster v geo master euclid::slave config use-tarssh blah Invalid value(blah) for option use-tarssh geo-replication command failed [root@pythagoras ]# gluster v geo master euclid::slave config use-tarssh gibber Invalid value(gibber) for option use-tarssh geo-replication command failed Now the valid values [root@pythagoras ]# gluster v geo master euclid::slave config use-tarssh true geo-replication config updated successfully [root@pythagoras ]# gluster v geo master euclid::slave config | grep tar use_tarssh: true ssh_command_tar: ssh -oPasswordAuthentication=no -oStrictHostKeyChecking=no -i /var/lib/glusterd/geo-replication/tar_ssh.pem [root@pythagoras ]# gluster v geo master euclid::slave config use-tarssh false geo-replication config updated successfully [root@pythagoras ]# gluster v geo master euclid::slave config | grep tar use_tarssh: false ssh_command_tar: ssh -oPasswordAuthentication=no -oStrictHostKeyChecking=no -i /var/lib/glusterd/geo-replication/tar_ssh.pem [root@pythagoras ]# gluster v geo master euclid::slave config use-tarssh 1 geo-replication config updated successfully [root@pythagoras ]# gluster v geo master euclid::slave config | grep tar use_tarssh: 1 ssh_command_tar: ssh -oPasswordAuthentication=no -oStrictHostKeyChecking=no -i /var/lib/glusterd/geo-replication/tar_ssh.pem [root@pythagoras ]# gluster v geo master euclid::slave config use-tarssh 0 geo-replication config updated successfully [root@pythagoras ]# gluster v geo master euclid::slave config | grep tar use_tarssh: 0 ssh_command_tar: ssh -oPasswordAuthentication=no -oStrictHostKeyChecking=no -i /var/lib/glusterd/geo-replication/tar_ssh.pem Not it takes only true, false, yes, no, 1 and 0 as valid values. So moving the bug to verified.
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. http://rhn.redhat.com/errata/RHBA-2013-1769.html