Bug 1507752

Summary:	Brick port mismatch
Product:	[Community] GlusterFS	Reporter:	Gaurav Yadav <gyadav>
Component:	glusterd	Assignee:	Gaurav Yadav <gyadav>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	3.10	CC:	abhishku, amukherj, bmekala, bugs, rhs-bugs, storage-qa-internal, vbellur
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.10.8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1506589	Environment:
Last Closed:	2017-12-08 16:46:32 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:	1505433, 1506589
Bug Blocks:	1507748

Description Gaurav Yadav 2017-10-31 04:57:24 UTC

+++ This bug was initially created as a clone of Bug #1506589 +++

Description of problem:

After force start of the volume, brick port mismatch between volume status and ps output.

Version-Release number of selected component (if applicable):

RHGS 3.3


Actual results:

Brick port is different in both volume status and ps output.


Expected results:


Brick port should be same in both volume status and ps output.

Comment 1 Worker Ant 2017-10-31 05:19:37 UTC

REVIEW: https://review.gluster.org/18590 (glusterd: persist brickinfo's port change into glusterd's store) posted (#1) for review on release-3.10 by Gaurav Yadav

Comment 2 Worker Ant 2017-10-31 18:07:39 UTC

COMMIT: https://review.gluster.org/18590 committed in release-3.10 by  

------------- glusterd: persist brickinfo's port change into glusterd's store

Problem:
Consider a case where node reboot is performed and prior to reboot
brick was listening to 49153. Post reboot glusterd assigned 49152
to brick and started the brick process but the new port was never
persisted. Now when glusterd restarts glusterd always read the port
from its persisted store i.e 49153 however pmap signin happens with
the correct port i.e 49152.

Fix:
Make sure when glusterd_brick_start is called, glusterd_store_volinfo is
eventually invoked.

Change-Id: Ic0efbd48c51d39729ed951a42922d0e59f7115a1
BUG: 1507752
Signed-off-by: Gaurav Yadav <gyadav>

Comment 3 Shyamsundar 2017-12-08 16:46:32 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.10.8, please open a new bug report.

glusterfs-3.10.8 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://lists.gluster.org/pipermail/announce/2017-December/000086.html
[2] https://www.gluster.org/pipermail/gluster-users/