Bug 1409078 - RFE: Need a command to check op-version compatibility of clients
Summary: RFE: Need a command to check op-version compatibility of clients
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: mainline
Hardware: All
OS: All
medium
medium
Target Milestone: ---
Assignee: Samikshan Bairagya
QA Contact:
URL:
Whiteboard:
: 1273956 (view as bug list)
Depends On: 1302944
Blocks: 1304366
TreeView+ depends on / blocked
 
Reported: 2016-12-29 10:34 UTC by Samikshan Bairagya
Modified: 2017-03-08 17:27 UTC (History)
7 users (show)

Fixed In Version: glusterfs-3.10.0
Doc Type: Enhancement
Doc Text:
Clone Of: 1302944
Environment:
Last Closed: 2017-03-06 17:41:22 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Samikshan Bairagya 2016-12-29 10:34:44 UTC
+++ 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)

Comment 1 Worker Ant 2016-12-29 11:47:56 UTC
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)

Comment 2 Worker Ant 2017-01-02 12:32:55 UTC
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)

Comment 3 Worker Ant 2017-01-03 09:13:18 UTC
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)

Comment 4 Worker Ant 2017-01-10 11:32:13 UTC
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)

Comment 5 Worker Ant 2017-01-12 18:21:03 UTC
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>

Comment 6 Shyamsundar 2017-03-06 17:41:22 UTC
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/

Comment 7 Joe Julian 2017-03-08 17:27:37 UTC
*** Bug 1273956 has been marked as a duplicate of this bug. ***


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