Description of problem: Dist-geo-rep : in case of hostname unreachable, 'gluster volume geo <mater_vol> <slave_ip>::<slvae_vol> start/stop/config' says 'Staging failed on localhost' Version-Release number of selected component (if applicable): 3.4.0.12rhs.beta6-1.el6rhs.x86_64 How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: [root@DVM1 ~]# gluster volume geo test5 abc.lab.eng.blr.redhat.com::slavecon stop Staging failed on localhost. Please check the log file for more details. geo-replication command failed [root@DVM1 ~]# gluster volume geo test5 abc.lab.eng.blr.redhat.com::slavecon start Staging failed on localhost. Please check the log file for more details. geo-replication command failed [root@DVM1 ~]# gluster volume geo test5 abc.lab.eng.blr.redhat.com::slavecon config Staging failed on localhost. Please check the log file for more details. geo-replication command failed Expected results: slave host abc.lab.eng.blr.redhat.com does not exist and there is no geo rep session with that host. start/stop/config should say there is no geo rep session between master and slave rather than staging failed error Additional info:
Fix is in the patch https://code.engineering.redhat.com/gerrit/11204
In case of unreachable and invalid Ip's like a.b.c.d, the cli will display a.b.c.d. is not reachable.
Agree with comment #3 and the error message. This does not need to be a blocker but should be fixed in RHSS 2.1.
Taken in. Url: same as comment #2
verified with 3.4.0.20rhs-2.el6rhs.x86_64 working as mentioned in comment #3, hence changing status 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-1262.html