Bug 1612418

Summary:	Brick not coming up on a volume after rebooting the node
Product:	[Community] GlusterFS	Reporter:	Mohit Agrawal <moagrawa>
Component:	glusterd	Assignee:	Mohit Agrawal <moagrawa>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bmekala, bugs, rhs-bugs, sankarshan, storage-qa-internal, ubansal, vbellur
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-5.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1612098	Environment:
Last Closed:	2018-10-23 15:16:17 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:	1612098
Bug Blocks:

Comment 1 Mohit Agrawal 2018-08-04 06:11:58 UTC

RCA:

Brick is not coming up after reboot because of fsid comparison failing at the
time of start brick. The fsid comparison is failed because fsid is changed after
reboot the node.To resolve the same compare volume_id xattr with saved volume_uid before start/attach a brick.volume_id is populated on a brick_root path at the time of creating a volume and same volume_id is stored on the backend by glusterd.


Thanks
Mohit Agrawal

Comment 2 Worker Ant 2018-08-04 06:44:50 UTC

REVIEW: https://review.gluster.org/20638 (glusterd: Compare volume_id before start/attach a brick) posted (#1) for review on master by MOHIT AGRAWAL

Comment 3 Worker Ant 2018-08-10 17:52:07 UTC

COMMIT: https://review.gluster.org/20638 committed in master by "Atin Mukherjee" <amukherj> with a commit message- glusterd: Compare volume_id before start/attach a brick

Problem: After reboot a node brick is not coming up because
         fsid comparison is failed before start a brick

Solution: Instead of comparing fsid compare volume_id to
          resolve the same because fsid is changed after
          reboot a node but volume_id persist as a xattr
          on brick_root path at the time of creating a volume.

Change-Id: Ic289aab1b4ebfd83bbcae8438fee26ae61a0fff4
fixes: bz#1612418
Signed-off-by: Mohit Agrawal <moagrawal>

Comment 4 Shyamsundar 2018-10-23 15:16:17 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-5.0, please open a new bug report.

glusterfs-5.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] https://lists.gluster.org/pipermail/announce/2018-October/000115.html
[2] https://www.gluster.org/pipermail/gluster-users/