Bug 1651460

Summary:	glusterd can't regenerate volfiles in container storage upgrade workflow
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Atin Mukherjee <amukherj>
Component:	glusterd	Assignee:	Atin Mukherjee <amukherj>
Status:	CLOSED ERRATA	QA Contact:	Bala Konda Reddy M <bmekala>
Severity:	high	Docs Contact:
Priority:	medium
Version:	rhgs-3.4	CC:	amukherj, kiyer, rcyriac, rhs-bugs, sankarshan, srakonde, srmukher, storage-qa-internal, vbellur
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 3.4.z Batch Update 3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.12.2-33	Doc Type:	Bug Fix
Doc Text:	Earlier, the glusterd service did not regenerate volfiles during initialization when there was a change in the maximum operating version supported. This resulted in bricks running with an older volfile in Red Hat OpenShift Container Storage. With this fix, glusterd will regenerate the volfiles whenever there is a variation in the maximum (max-op-version) supported operating version.	Story Points:	---
Clone Of:
Clones:	1651463 (view as bug list)		Environment:
Last Closed:	2019-02-04 07:41:26 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:	1651463
Bug Blocks:	1651038

Description Atin Mukherjee 2018-11-20 07:11:07 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):
RHGS 3.4/OCS 3.10

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 15 Srijita Mukherjee 2019-01-20 19:23:41 UTC

The doc text has been updated. Kindly review the technical accuracy.

Comment 16 Atin Mukherjee 2019-01-21 02:42:27 UTC

Made some modification and signing it off.

Comment 18 errata-xmlrpc 2019-02-04 07:41:26 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:0263