+++ This bug was initially created as a clone of Bug #1234842 +++ 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/11395 (glusterd: Store peerinfo after updating hostnames) posted (#1) for review on release-3.6 by Kaushal M (kaushal)
REVIEW: http://review.gluster.org/11395 (glusterd: Store peerinfo after updating hostnames) posted (#2) for review on release-3.6 by Kaushal M (kaushal)
COMMIT: http://review.gluster.org/11395 committed in release-3.6 by Raghavendra Bhat (raghavendra) ------ commit d35d7c1bf986cacb65da912123b9a34ebe946bef Author: Kaushal M <kaushal> Date: Tue Jun 23 15:40:59 2015 +0530 glusterd: Store peerinfo after updating hostnames Backport of https://review.gluster.org/11365 Change-Id: I1d36ac63de810061d60edb28b6f591ae45d5cd3a BUG: 1234846 Signed-off-by: Kaushal M <kaushal> Reviewed-on: http://review.gluster.org/11395 Tested-by: Gluster Build System <jenkins.com> Tested-by: NetBSD Build System <jenkins.org> Reviewed-by: Raghavendra Bhat <raghavendra>