Description of problem:
when processing "gluster v status [vol] nfs clients" after "systemctl restart glusterd", gnfs will crash with certain probability.
dump trace info:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create replicate volume naming rep
2. set rep volume nfs.disable off
3. process cli: "systemctl restart glusterd; gluster volume status rep nfs clients"
REVIEW: https://review.gluster.org/21569 (glusterfsd: Do not process GLUSTERD_NODE_STATUS if graph is not ready) posted (#1) for review on master by Hu Jianfei
REVIEW: https://review.gluster.org/21569 (glusterfsd: Do not process GLUSTERD_NODE_STATUS if graph is not ready) posted (#4) for review on master by Amar Tumballi
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 , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.