+++ This bug was initially created as a clone of Bug #1302944 +++ Description of problem: This enhancement is discussed in detail @http://www.gluster.org/pipermail/gluster-users/2016-January/025090.html Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: --- Additional comment from Worker Ant on 2016-12-28 10:27:32 EST --- REVIEW: http://review.gluster.org/16303 (glusterd: Add info on op-version for clients in vol status output) posted (#1) for review on master by Samikshan Bairagya (samikshan)
REVIEW: http://review.gluster.org/16303 (glusterd: Add info on op-version for clients in vol status output) posted (#2) for review on master by Samikshan Bairagya (samikshan)
REVIEW: http://review.gluster.org/16303 (glusterd: Add info on op-version for clients in vol status output) posted (#3) for review on master by Samikshan Bairagya (samikshan)
REVIEW: http://review.gluster.org/16303 (glusterd: Add info on op-version for clients in vol status output) posted (#4) for review on master by Samikshan Bairagya (samikshan)
REVIEW: http://review.gluster.org/16303 (glusterd: Add info on op-version for clients in vol status output) posted (#5) for review on master by Samikshan Bairagya (samikshan)
COMMIT: http://review.gluster.org/16303 committed in master by Atin Mukherjee (amukherj) ------ commit 2e5383266869c13ee27ceaee5b24b686e2415df4 Author: Samikshan Bairagya <samikshan> Date: Wed Dec 28 20:33:54 2016 +0530 glusterd: Add info on op-version for clients in vol status output Currently the `gluster volume status <VOLNAME|all> clients` command gives us the following information on clients: 1. Brick name 2. Client count for each brick 3. hostname:port for each client 4. Bytes read and written for each client There is no information regarding op-version for each client. This patch adds that to the output. Change-Id: Ib2ece93ab00c234162bb92b7c67a7d86f3350a8d BUG: 1409078 Signed-off-by: Samikshan Bairagya <samikshan> Reviewed-on: http://review.gluster.org/16303 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Atin Mukherjee <amukherj>
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/
*** Bug 1273956 has been marked as a duplicate of this bug. ***