Description of problem: Distributed-geo-rep : If geo rep session is not started and user execute stop command, it gives error "Staging failed on ..Please check the log file for more details." instead of telling session is not started Version-Release number of selected component (if applicable): 3.4.0.12rhs.beta1-1.el6rhs.x86_64 How reproducible: always Steps to Reproduce: 1. do all necessary setp tp create georep session 2.create geo rep session 3.now stop it before starting [root@hulk ~]# gluster volume geo master2 10.70.43.147::slave2 create force Creating geo-replication session between master2 & 10.70.43.147::slave2 has been successful [root@hulk ~]# gluster volume geo master2 10.70.43.147::slave2 status NODE MASTER SLAVE HEALTH UPTIME ------------------------------------------------------------------------------------------- wall.blr.redhat.com master2 10.70.43.147::slave2 Not Started N/A lannister.blr.redhat.com master2 10.70.43.147::slave2 Not Started N/A ironman.blr.redhat.com master2 10.70.43.147::slave2 Not Started N/A [root@hulk ~]# gluster volume geo master2 10.70.43.147::slave2 stop Staging failed on 10.70.42.246. Please check the log file for more details. Staging failed on 10.70.42.191. Please check the log file for more details. Staging failed on 10.70.42.158. Please check the log file for more details. geo-replication command failed Actual results: Staging failed on 10.70.42.246. Please check the log file for more details. Staging failed on 10.70.42.191. Please check the log file for more details. Staging failed on 10.70.42.158. Please check the log file for more details. geo-replication command failed from log file we can see that session is not started Expected results: It's better to inform User that session is not started. Additional info:
verified on 3.4.0.14rhs-1.el6rhs.x86_64
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-1262.html