Bug 1537364

Summary:	[RFE] - get-state option should mark profiling enabled flag at volume level
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:	bmekala, bugs, rhs-bugs, shtripat, storage-qa-internal, vbellur
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-v4.1.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1537357	Environment:
Last Closed:	2018-06-20 17:58:10 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:	1537357

Comment 1 Atin Mukherjee 2018-01-23 02:54:24 UTC

Description of problem:
There is no information about profiling enabled/not-started at volume level in get-state output

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


How reproducible:
Always

Steps to Reproduce:
1. Setup a gluster cluster with 3 nodes
2. Create a dist-replicate volume
3. Start volume profile on the volume
4. Run the command `gluster get-state` and check the output

Actual results:
There is not detail of volume profiling enaled

Expected results:
The get-state output should mention if volume profiling is enabled/not-started for the volume

Comment 2 Worker Ant 2018-01-23 02:55:31 UTC

REVIEW: https://review.gluster.org/19286 (glusterd: add profile_enabled flag in get-state) posted (#1) for review on master by Atin Mukherjee

Comment 3 Worker Ant 2018-01-25 08:05:04 UTC

COMMIT: https://review.gluster.org/19286 committed in master by \"Atin Mukherjee\" <amukherj> with a commit message- glusterd: add profile_enabled flag in get-state

Change-Id: I09f348ed7ae6cd481f8c4d8b4f65f2f2f6aad84e
BUG: 1537364
Signed-off-by: Atin Mukherjee <amukherj>

Comment 4 Shyamsundar 2018-06-20 17:58:10 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-v4.1.0, please open a new bug report.

glusterfs-v4.1.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/announce/2018-June/000102.html
[2] https://www.gluster.org/pipermail/gluster-users/