Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1651463

Summary:	glusterd can't regenerate volfiles in container storage upgrade workflow
Product:	[Community] GlusterFS	Reporter:	Atin Mukherjee <amukherj>
Component:	glusterd	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	mainline	CC:	bmekala, bugs, rhs-bugs, sankarshan, storage-qa-internal, vbellur
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-6.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1651460	Environment:
Last Closed:	2019-03-25 16:32:04 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:
Bug Blocks:	1651460

Comment 1 Atin Mukherjee 2018-11-20 07:12:59 UTC

Description of problem:

Since in container storage mode when gluster versions are changed as part of an upgrade workflow glusterd isn't brought up in interim upgrade mode which results in gluster brick processes to start with old brick volfiles which isn't functionally correct.

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

How reproducible:
Always

Comment 2 Worker Ant 2018-11-20 07:14:59 UTC

REVIEW: https://review.gluster.org/21687 (glusterd: glusterd to regenerate volfiles on existence of glusterd.upgrade file) posted (#1) for review on master by Atin Mukherjee

Comment 3 Worker Ant 2018-12-05 21:36:59 UTC

REVIEW: https://review.gluster.org/21687 (glusterd: glusterd to regenerate volfiles when GD_OP_VERSION_MAX changes) posted (#6) for review on master by Amar Tumballi

Comment 4 Shyamsundar 2019-03-25 16:32:04 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-6.0, please open a new bug report.

glusterfs-6.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/2019-March/000120.html
[2] https://www.gluster.org/pipermail/gluster-users/