Bug 1273956 - status clients should show client version
status clients should show client version
Status: CLOSED DUPLICATE of bug 1409078
Product: GlusterFS
Classification: Community
Component: glusterd (Show other bugs)
All All
unspecified Severity unspecified
: ---
: ---
Assigned To: Atin Mukherjee
: Reopened, Triaged
Depends On:
  Show dependency treegraph
Reported: 2015-10-21 11:09 EDT by Joe Julian
Modified: 2017-03-08 12:27 EST (History)
2 users (show)

See Also:
Fixed In Version: 3.10.0
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-03-08 12:24:22 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Joe Julian 2015-10-21 11:09:21 EDT
I tried to set the read-subvolume to work around a different bug:

$ gluster volume set public cluster.read-subvolume public-client-0                      
volume set: failed: One or more connected clients cannot support the feature being set. These clients need to be upgraded or disconnected before running this command again

(Odd since read-subvolume has been in since 2.0)

So I looked to see what clients were connected:
$ gluster volume status public clients
Client connections for volume public
Brick : strabo:/data/gluster/fileshare/public
Clients connected : 6
Hostname                                               BytesRead    BytesWritten
--------                                               ---------    ------------                                       124640          121188                                        84624         1311300                                            960             600                                           964             600                                           4076            3596                                         29372           18264
Brick : nightshade:/data/gluster/fileshare/public
Clients connected : 4
Hostname                                               BytesRead    BytesWritten
--------                                               ---------    ------------                                          4088            3616                                            964             608                                            960             608                                         31840           20916

Which doesn't tell me which client could be the problem. Reporting the version, or at least the max-op-version, would be useful.
Comment 1 Atin Mukherjee 2015-10-25 23:32:29 EDT
I've a patch http://review.gluster.org/#/c/11831/ which addresses this problem in a bit different way. This patch enhances the log/output for a unsupported client. The patch needs some review attention before it gets into the codebase.
Comment 2 Kaushal 2017-03-08 05:49:39 EST
This bug is getting closed because GlusteFS-3.7 has reached its end-of-life.

Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS.
If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.
Comment 3 Atin Mukherjee 2017-03-08 12:24:22 EST
http://review.gluster.org/16303 addresses this issue and the same is already available in 3.10.0 release.
Comment 4 Joe Julian 2017-03-08 12:27:12 EST
Thanks, Atin. I missed that it was released since someone opened a duplicate of this bug without checking to see if one existed.
Comment 5 Joe Julian 2017-03-08 12:27:37 EST

*** This bug has been marked as a duplicate of bug 1409078 ***

Note You need to log in before you can comment on or make changes to this bug.