Bug 1663223

Summary:	profile info command is not displaying information of bricks which are hosted on peers
Product:	[Community] GlusterFS	Reporter:	Sanju <srakonde>
Component:	glusterd	Assignee:	Sanju <srakonde>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-6.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1663232 (view as bug list)		Environment:
Last Closed:	2019-03-25 16:32:53 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:	1663232

Description Sanju 2019-01-03 13:38:56 UTC

Description of problem:
When we run "gluster v profile <volname> info" from node n1, it is showing
information of bricks from local node only. Information of bricks which are hosted on peers is not shown in the output.

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


How reproducible:
always

Steps to Reproduce:
1. In a cluster of more than 1 node, create and start a volume
2. start profile for the volume
3. run gluster v profile volname info

Actual results:


Expected results:
it should display information of all the bricks of volume.

Additional info:

Comment 1 Worker Ant 2019-01-03 13:48:12 UTC

REVIEW: https://review.gluster.org/21988 (glusterd: aggregate rsp from peers) posted (#1) for review on master by Sanju Rakonde

Comment 2 Worker Ant 2019-01-03 17:48:37 UTC

REVIEW: https://review.gluster.org/21988 (glusterd: aggregate rsp from peers for profile command) posted (#2) for review on master by Atin Mukherjee

Comment 3 Shyamsundar 2019-03-25 16:32: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-6.0, please open a new bug report.

glusterfs-6.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] https://lists.gluster.org/pipermail/announce/2019-March/000120.html
[2] https://www.gluster.org/pipermail/gluster-users/