Description of problem: The volume status command doesn't display all the bricks when the cluster is a mixed cluster. It displays the bricks in the higher gluster version(3.8) but the bricks in the lower version (3.6) is not displayed. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1.create a mixed cluster with 3.6 and 3.8 2.create a volume wit bricks in both the nodes 3.Issue gluster v status Actual results: Status of volume: vol1 Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick 10.70.42.171:/data/gluster/tier/cbr2 49153 0 Y 13608 NFS Server on localhost N/A N/A N N/A NFS Server on dhcp42-203.lab.eng.blr.redhat .com N/A N/A N N/A Task Status of Volume vol1 ------------------------------------------------------------------------------ There are no active volume tasks Expected results: Status of volume: vol1 Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick 10.70.42.171:/data/gluster/tier/cbr2 49153 0 Y 31879 Brick 10.70.42.203:/data/gluster/tier/cbr2 49154 0 Y 27686 NFS Server on localhost N/A N/A N N/A NFS Server on dhcp42-203.lab.eng.blr.redhat .com N/A N/A N N/A Task Status of Volume vol1 ------------------------------------------------------------------------------ There are no active volume tasks Additional info: The brick on the host, 10.70.42.203 (3.6) was missing.
REVIEW: http://review.gluster.org/11986 (glusterd: volume status backward compatibility) posted (#1) for review on master by hari gowtham (hari.gowtham005)
REVIEW: http://review.gluster.org/11986 (glusterd: volume status backward compatibility) posted (#2) for review on master by hari gowtham (hari.gowtham005)
REVIEW: http://review.gluster.org/11986 (glusterd: volume status backward compatibility) posted (#3) for review on master by hari gowtham (hari.gowtham005)
REVIEW: http://review.gluster.org/11986 (glusterd: volume status backward compatibility) posted (#4) for review on master by hari gowtham (hari.gowtham005)
REVIEW: http://review.gluster.org/11986 (glusterd: volume status backward compatibility) posted (#5) for review on master by hari gowtham (hari.gowtham005)
REVIEW: http://review.gluster.org/11986 (glusterd: volume status backward compatibility) posted (#7) for review on master by hari gowtham (hari.gowtham005)
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.0, please open a new bug report. glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user