Bug 1651460 - glusterd can't regenerate volfiles in container storage upgrade workflow
Summary: glusterd can't regenerate volfiles in container storage upgrade workflow
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterd
Version: rhgs-3.4
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ---
: RHGS 3.4.z Batch Update 3
Assignee: Atin Mukherjee
QA Contact: Bala Konda Reddy M
URL:
Whiteboard:
Depends On: 1651463
Blocks: 1651038
TreeView+ depends on / blocked
 
Reported: 2018-11-20 07:11 UTC by Atin Mukherjee
Modified: 2019-02-07 07:18 UTC (History)
9 users (show)

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.
Clone Of:
: 1651463 (view as bug list)
Environment:
Last Closed: 2019-02-04 07:41:26 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1651038 0 urgent CLOSED [Tracker RHGS#1651460] OCS upgrade doesn't regenerate volfiles 2022-03-13 16:07:09 UTC
Red Hat Product Errata RHBA-2019:0263 0 None None None 2019-02-04 07:41:37 UTC

Internal Links: 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
Note You need to log in before you can comment on or make changes to this bug.