During a friend update, if glusterd updated the hostnames of a peerinfo object, it wouldn't store the updated peerinfo object. This could cause brick resolution to fail on glusterd restart if the bricks used hostname from the newly added hostnames.
REVIEW: http://review.gluster.org/11365 (glusterd: Store peerinfo after updating hostnames) posted (#1) for review on master by Kaushal M (kaushal)
REVIEW: http://review.gluster.org/11365 (glusterd: Store peerinfo after updating hostnames) posted (#2) for review on master by Kaushal M (kaushal)
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.
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