Bug 1396807

Summary:	capture volume tunables in get-state dump
Product:	[Community] GlusterFS	Reporter:	Atin Mukherjee <amukherj>
Component:	glusterd	Assignee:	Atin Mukherjee <amukherj>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.10.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1397257 1397352 (view as bug list)		Environment:
Last Closed:	2017-03-06 17:35:27 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:
Bug Depends On:
Bug Blocks:	1397257, 1397352

Description Atin Mukherjee 2016-11-20 12:50:20 UTC

Description of problem:

get-state output doesn't capture volinfo->dict

Version-Release number of selected component (if applicable):
mainline

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2016-11-20 12:53:07 UTC

REVIEW: http://review.gluster.org/15889 (glusterd: dump volinfo->dict in gluster get-state) posted (#1) for review on master by Atin Mukherjee (amukherj)

Comment 2 Worker Ant 2016-11-22 11:09:17 UTC

COMMIT: http://review.gluster.org/15889 committed in master by Atin Mukherjee (amukherj) 
------
commit 7b80a0f02fa0c27f5f5e89e69f92678145fd6a7f
Author: Atin Mukherjee <amukherj>
Date:   Sun Nov 20 18:18:45 2016 +0530

    glusterd: dump volinfo->dict in gluster get-state
    
    Change-Id: I7e60629fb8003c620847fa63441f6b098db59721
    BUG: 1396807
    Signed-off-by: Atin Mukherjee <amukherj>
    Reviewed-on: http://review.gluster.org/15889
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Samikshan Bairagya <samikshan>
    Reviewed-by: Rohan Kanade <rkanade>

Comment 3 Shyamsundar 2017-03-06 17:35:27 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/