Bug 1267680

Summary:	RFE: provide more details on the clients (gluser version at minimum) when reporting gluster volume status xxxx clients
Product:	[Community] GlusterFS	Reporter:	Alastair Neil <aneil2>
Component:	cli	Assignee:	Atin Mukherjee <amukherj>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	mainline	CC:	bugs
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	glusterfs-4.1.3 (or higher)	Doc Type:	Enhancement
Doc Text:	Feature: Improving gluster v status <volname> clients Reason: Result:	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-08-29 03:17:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Alastair Neil 2015-09-30 16:03:18 UTC

Description of problem:
when large numbers of clients are connected it is a challenge to track down which client has an out of date version of gluster.  Often setting new features is stymied by a handful of clients with older versions. 

Version-Release number of selected component (if applicable):
3.7.4 and earlier

How reproducible:
always

Steps to Reproduce:
1.run: gluster volume status <volname> clients
2.
3.

Actual results:
receive list of client hostnames and bytes read and bytes written

Expected results:
receive list of clients with useful information such as, at a minimum, glusterfs client version.  Possibly highlight peers. etc.


Additional info:

Comment 1 Atin Mukherjee 2017-01-23 15:45:37 UTC

This is fixed as part of BZ 1409078