Description of problem: geo-replication create push pem does not validate the volume name which does not exist and returns simply a success message. Version-Release number of selected component (if applicable): How reproducible: execute gluster volume geo-replication <(any)volume name which does not exists in master> slave_host::slave_vol create push-pem Actual results: Expected results: should say volume does not exist Additional info: [root@rhsc-test gluster]# gluster --version glusterfs 3.4.0.14rhs built on Jul 30 2013 09:09:36 Repository revision: git://git.gluster.com/glusterfs.git Copyright (c) 2006-2011 Gluster Inc. <http://www.gluster.com> GlusterFS comes with ABSOLUTELY NO WARRANTY. You may redistribute copies of GlusterFS under the terms of the GNU General Public License. [root@rhsc-test gluster]# cat /etc/redhat-release Red Hat Enterprise Linux Server release 6.4 (Santiago)
Working with RHS 3.0. Don't intend backporting to 2.1.z.
Works as expected with latest 3.1.2 build: [root@dhcp46-96 ~]# gluster volume list gluster_shared_storage master [root@dhcp46-96 ~]# gluster volume geo-replication mAster 10.70.47.94::slave create push-pem force Volume mAster does not exist geo-replication command failed [root@dhcp46-96 ~]# gluster volume geo-replication master 10.70.47.94::slAve create push-pem force Unable to fetch slave volume details. Please check the slave cluster and slave volume. geo-replication command failed [root@dhcp46-96 ~]# rpm -qa | grep glusterfs-geo-replication glusterfs-geo-replication-3.7.5-19.el6rhs.x86_64 [root@dhcp46-96 ~]# Patch is not going to be backported state for 2.1.z Should we close this bug as working in current release?