+++ 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:
REVIEW: http://review.gluster.org/16442 (cli: keep 'gluster volume status detail' consistent) posted (#1) for review on release-3.8 by Xavier Hernandez (xhernandez)
COMMIT: https://review.gluster.org/16442 committed in release-3.8 by Atin Mukherjee (amukherj) ------ commit 644ca6d8656e323a142c0a3cd2942ff5ce718785 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: I01f99562dddff5d5cb6974df44d1b6366faf05dc BUG: 1415132 Signed-off-by: Xavier Hernandez <xhernandez> Reviewed-on: https://review.gluster.org/16442 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Kaleb KEITHLEY <kkeithle>
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.8.9, please open a new bug report. glusterfs-3.8.9 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/2017-February/000066.html [2] https://www.gluster.org/pipermail/gluster-users/