Bug 1415133

Summary:	Improve output of "gluster volume status detail"
Product:	[Community] GlusterFS	Reporter:	Xavi Hernandez <jahernan>
Component:	glusterd	Assignee:	Xavi Hernandez <jahernan>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.7.18	CC:	amukherj, bugs, kjohnson
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.7.20	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1411334	Environment:
Last Closed:	2017-02-01 11:38:22 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:	1411334, 1416416
Bug Blocks:

Description Xavi Hernandez 2017-01-20 11:19:09 UTC

+++ This bug was initially created as a clone of Bug #1411334 +++

Description of problem:

Currently "gluster volume status detail" only gives all available information for linux hosts. Additionally, if the command is executed from a FreeBSD node, some brick information is hidden, even if it comes from a linux brick.


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


How reproducible:

Always

Steps to Reproduce:
1. Create a distributed volume with one brick on CentOS and another one on FreeBSD
2. Run gluster volume status <volname> detail on CentOS
3. Run gluster volume status <volname> detail on FreeBSD

Actual results:

On CentOS, some information from the brick hosted by FreeBSD appears as "N/A". On FreeBSD some information is missing, even from the CentOS brick.

Expected results:

Both commands should return the same output and all available info should be filled instead of writing "N/A".

Additional info:

Comment 1 Worker Ant 2017-01-20 11:25:12 UTC

REVIEW: http://review.gluster.org/16443 (cli: keep 'gluster volume status detail' consistent) posted (#1) for review on release-3.7 by Xavier Hernandez (xhernandez)

Comment 2 Worker Ant 2017-01-25 04:51:33 UTC

COMMIT: https://review.gluster.org/16443 committed in release-3.7 by Atin Mukherjee (amukherj) 
------
commit 912c3b58717f03453fedbb6c15482c052bdcd847
Author: Xavier Hernandez <xhernandez>
Date:   Tue Jan 10 11:21:06 2017 +0100

    cli: keep 'gluster volume status detail' consistent
    
    The output of the command 'gluster volume status <volname> detail' is
    not consistent between operating systems. On linux hosts it shows the
    file system type, the device name, mount options and inode size of each
    brick. However the same command executed on a FreeBSD host doesn't show
    all this information, even for bricks stored on a linux.
    
    Additionally, for hosts other than linux, this information is shown as
    'N/A' many times. This has been fixed to show as much information as it
    can be retrieved from the operating system.
    
    The file contrib/mount/mntent.c has been mostly rewriten because it
    contained many errors that caused mount information to not be retrieved
    on some operating systems.
    
    > Change-Id: Icb6e19e8af6ec82255e7792ad71914ef679fc316
    > BUG: 1411334
    > Signed-off-by: Xavier Hernandez <xhernandez>
    > Reviewed-on: http://review.gluster.org/16371
    > 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>
    > Reviewed-by: Kaleb KEITHLEY <kkeithle>
    
    Change-Id: Ic1a40546eef3befb16310ab5e022d83bbbc946d5
    BUG: 1415133
    Signed-off-by: Xavier Hernandez <xhernandez>
    Reviewed-on: https://review.gluster.org/16443
    Smoke: Gluster Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle>
    NetBSD-regression: NetBSD Build System <jenkins.org>

Comment 3 Kaushal 2017-02-01 11:38: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.7.20, please open a new bug report.

glusterfs-3.7.20 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/gluster-devel/2017-January/052010.html
[2] https://www.gluster.org/pipermail/gluster-users/