Bug 1234843

Summary:	GlusterD does not store updated peerinfo objects.
Product:	[Community] GlusterFS	Reporter:	Kaushal <kaushal>
Component:	glusterd	Assignee:	Kaushal <kaushal>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	high
Version:	3.7.1	CC:	amukherj, bugs, gluster-bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.7.3	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1234842	Environment:
Last Closed:	2015-07-30 09:49:42 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1234842
Bug Blocks:	1233025, 1234725

Description Kaushal 2015-06-23 11:27:00 UTC

+++ 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.

Comment 1 Anand Avati 2015-06-26 04:22:15 UTC

REVIEW: http://review.gluster.org/11394 (glusterd: Store peerinfo after updating hostnames) posted (#2) for review on release-3.7 by Kaushal M (kaushal)

Comment 2 Anand Avati 2015-06-26 08:28:53 UTC

COMMIT: http://review.gluster.org/11394 committed in release-3.7 by Atin Mukherjee (amukherj) 
------
commit 84396c9834a83b73f6b689d078bb206667cc3f3f
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: 1234843
    Signed-off-by: Kaushal M <kaushal>
    Reviewed-on: http://review.gluster.org/11394
    Tested-by: NetBSD Build System <jenkins.org>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Atin Mukherjee <amukherj>

Comment 3 Kaushal 2015-07-30 09:49:42 UTC

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.7.3, please open a new bug report.

glusterfs-3.7.3 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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/12078
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user