Hide Forgot
+++ This bug was initially created as a clone of Bug #843838 +++ Description of problem: 'gluster vol geo-rep status detail' doesn't work. It only works when master and slave volume args are given. Version-Release number of selected component (if applicable): mainline How reproducible: Always Steps to Reproduce: 1.Create a glustervolume and a Geo replication session 2.Run 'gluster vol geo-rep status detail' Actual results: The command fails with incorrect usage Expected results: It should not fail. Additional info:
REVIEW: http://review.gluster.org/16347 (cli/src/cli-cmd-parser.c: Updated 'gluster vol geo-rep status detail') posted (#1) for review on master by Sonal Arora (sarora@redhat.com)
REVIEW: http://review.gluster.org/16347 (cli/geo-rep: Fix geo-rep status detail) posted (#2) for review on master by Sonal Arora (sarora@redhat.com)
REVIEW: http://review.gluster.org/16347 (cli/geo-rep: Fix geo-rep status detail) posted (#3) for review on master by Sonal Arora (sarora@redhat.com)
COMMIT: http://review.gluster.org/16347 committed in master by Jeff Darcy (jdarcy@redhat.com) ------ commit 27c85d014bb7d03c323e08038d9c6db538d632fb Author: SonaArora <sarora@redhat.com> Date: Fri Jan 6 14:21:56 2017 +0530 cli/geo-rep: Fix geo-rep status detail Earlier this command works when master and slave volume args are given. Now it works even when no volume args are given (i.e. 'gluster volume geo-replication status detail) and also when master volume is given (i.e.'gluster volume geo-replication <master-vol> status detail'). BUG: 1410071 Signed-off-by: SonaArora <sarora@redhat.com> Change-Id: I1a39241a4a5d70c20b2326599b3cccd8f1f6dc78 Reviewed-on: http://review.gluster.org/16347 Smoke: Gluster Build System <jenkins@build.gluster.org> Tested-by: Kotresh HR <khiremat@redhat.com> NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org> CentOS-regression: Gluster Build System <jenkins@build.gluster.org> Reviewed-by: Kotresh HR <khiremat@redhat.com>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.10.0, please open a new bug report. glusterfs-3.10.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/gluster-users/2017-February/030119.html [2] https://www.gluster.org/pipermail/gluster-users/