Bug 1718215

Summary:	Test datacenter upgrade from 4.3.4 + gluster 5 to 4.3.5 + gluster 6
Product:	[oVirt] ovirt-distribution	Reporter:	Sandro Bonazzola <sbonazzo>
Component:	glusterfs	Assignee:	Sachidananda Urs <surs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	4.3.5	CC:	sasundar
Target Milestone:	ovirt-4.3.5	Flags:	sbonazzo: ovirt-4.3? sbonazzo: blocker?
Target Release:	4.3.5
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-07-30 14:08:40 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Gluster	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1693998

Description Sandro Bonazzola 2019-06-07 09:28:17 UTC

We need to ensure that the upgrade flow from oVirt 4.3.4 + gluster 5 to oVirt 4.3.5 + gluster 6 is smooth and without surprises. We don't want to repeat the experience with the upgrade from gluster 3 to gluster 5.

This is a blocker for 4.3.5: either upgrade is flawless or we can't switch to gluster 6 in 4.3.5.

Comment 1 SATHEESARAN 2019-07-18 07:25:29 UTC

This is the pure upstream bug.

Downstream variant of Gluster (i.e) Red Hat Gluster Storage(RHGS) was never qualified with gluster-5

The upgrade testing was from RHGS 3.4.4 ( gluster-3.12.2-47.2 ) to RHGS 3.5.0 ( glusterfs-6.0-7 ) and
that was smooth with no issues found.
Based on the above fact verifying this bug for upgrade from RHGS 3.4.4 to RHGS 3.5.0

Comment 2 Sandro Bonazzola 2019-07-30 14:08:40 UTC

This bugzilla is included in oVirt 4.3.5 release, published on July 30th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.5 release, it has been closed with a resolution of CURRENT RELEASE.

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