Bug 1429541

Summary:	Rebase on Gluster 3.12
Product:	[oVirt] ovirt-release	Reporter:	Sandro Bonazzola <sbonazzo>
Component:	CentOS	Assignee:	Sandro Bonazzola <sbonazzo>
Status:	CLOSED CURRENTRELEASE	QA Contact:	SATHEESARAN <sasundar>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	---	CC:	bugs, pbrilla, sbonazzo
Target Milestone:	ovirt-4.2.0	Keywords:	Rebase
Target Release:	4.2.0	Flags:	rule-engine: ovirt-4.2+ sasundar: testing_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Rebase: Enhancements Only
Doc Text:	oVirt release now enables CentOS Storage SIG Gluster 3.10 repository. See Gluster 3.10 release notes for more information at https://gluster.readthedocs.io/en/latest/release-notes/3.10.0/	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-04 10:43:34 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Integration	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Sandro Bonazzola 2017-03-06 14:46:42 UTC

Gluster 3.10 has been released, we should change repositories from 3.8 to 3.10 to consume it.

Comment 1 Yaniv Kaul 2017-03-12 12:21:43 UTC

Rebase where? What does this bug mean?

Comment 2 Sandro Bonazzola 2017-03-15 12:31:46 UTC

We're currently requiring gluster 3.8 from CentOS Storage SIG.
We need to change the release yum repository config to use gluster 3.10 repository instead.

Comment 3 Sandro Bonazzola 2017-09-22 13:19:49 UTC

Requirement changed, we need to rebase on 3.12.

Comment 4 Red Hat Bugzilla Rules Engine 2017-09-22 13:19:54 UTC

Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 5 SATHEESARAN 2018-05-03 17:56:35 UTC

glusterfs 3.12 is consumed with ovirt-4.2.2

Comment 6 Sandro Bonazzola 2018-05-04 10:43:34 UTC

This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

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