Bug 1199451 - gluster command should retrieve current op-version of the NODE
Summary: gluster command should retrieve current op-version of the NODE
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: mainline
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Gaurav Kumar Garg
QA Contact:
URL:
Whiteboard:
Depends On: 1102047
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-06 10:40 UTC by Gaurav Kumar Garg
Modified: 2016-06-05 23:38 UTC (History)
10 users (show)

Fixed In Version: glusterfs-3.7.0
Doc Type: Enhancement
Doc Text:
Clone Of: 1102047
Environment:
Last Closed: 2015-05-14 17:29:18 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Gaurav Kumar Garg 2015-03-06 10:40:10 UTC
+++ This bug was initially created as a clone of Bug #1102047 +++

Description of problem:
-----------------------
op-version is set using the option 'cluster.op-version'.
There should be a way to get the current op-version on the RHS Node

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
RHS 3.0 ( glusterfs-3.6.0.8-1.el6rhs )

How reproducible:
-----------------
Not Applicable as its a enhancement

Steps to Reproduce:
------------------
Not Applicable

Actual results:
---------------
No way to get the op-version supported on the RHS Node, other than looking at glusterd.info file

Expected results:
-----------------
1. There should be a way to get the op-version on RHS Node

Additional info:

Comment 1 Anand Avati 2015-03-06 10:49:06 UTC
REVIEW: http://review.gluster.org/9821 (glusterd: gluster command should retrieve current op-version of the NODE) posted (#1) for review on master by Gaurav Kumar Garg (ggarg)

Comment 2 Gaurav Kumar Garg 2015-03-06 10:51:52 UTC
now with this fix user will able to get current op-version of the node by using command

# gluster volume get <vol-name> cluster.op-version

Comment 3 Anand Avati 2015-03-13 10:35:06 UTC
REVIEW: http://review.gluster.org/9821 (glusterd: gluster command should retrieve current op-version of the NODE) posted (#2) for review on master by Gaurav Kumar Garg (ggarg)

Comment 4 Anand Avati 2015-03-31 12:44:17 UTC
REVIEW: http://review.gluster.org/9821 (glusterd: gluster command should retrieve current op-version of the NODE) posted (#3) for review on master by Gaurav Kumar Garg (ggarg)

Comment 5 Anand Avati 2015-04-01 12:50:49 UTC
COMMIT: http://review.gluster.org/9821 committed in master by Kaushal M (kaushal) 
------
commit 2b949eb89e8ca22d2928c05d549b6f722adf1544
Author: Gaurav Kumar Garg <ggarg>
Date:   Fri Mar 6 16:11:16 2015 +0530

    glusterd: gluster command should retrieve current op-version of the NODE
    
    Problem:
    glusterd was failing to get some specific volume option. for eg:
    gluster volume get <vol-name> cluster.op-version
    
    Fix:
    glusterd should set count value in dictionary while retrieving specific volume
    option.
    
    Change-Id: Iada768ea3d8a0006895525eca2c2dcc40432a4ea
    BUG: 1199451
    Signed-off-by: Gaurav Kumar Garg <ggarg>
    Reviewed-on: http://review.gluster.org/9821
    Reviewed-by: Atin Mukherjee <amukherj>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Kaushal M <kaushal>

Comment 6 Niels de Vos 2015-05-14 17:29:18 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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 7 Niels de Vos 2015-05-14 17:35:53 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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 8 Niels de Vos 2015-05-14 17:38:14 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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 9 Niels de Vos 2015-05-14 17:46:13 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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user


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