Bug 1429537 - [RFE] Rebase on gluster-3.12
Summary: [RFE] Rebase on gluster-3.12
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-hosted-engine-setup
Classification: oVirt
Component: Plugins.Gluster
Version: ---
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.2.0
: 2.2.0
Assignee: Sandro Bonazzola
QA Contact: Nikolai Sednev
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-06 14:43 UTC by Sandro Bonazzola
Modified: 2017-12-20 11:17 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-12-20 11:17:06 UTC
oVirt Team: Integration
Embargoed:
rule-engine: ovirt-4.2?
mavital: testing_plan_complete-
nsednev: planning_ack?
sbonazzo: devel_ack+
rule-engine: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 82113 0 master MERGED packaging: spec: require gluster >= 3.12 2017-10-09 20:34:51 UTC

Description Sandro Bonazzola 2017-03-06 14:43:24 UTC 
Gluster 3.10 has been released, we need to make sure hosted engine works with it.
Comment 1 Yaniv Lavi 2017-06-12 12:59:12 UTC 
What is the right target for this?
Comment 2 Sandro Bonazzola 2017-06-13 12:54:59 UTC 
I think 4.2 but I let gluster people to confirm. Sahina?
Comment 3 Sahina Bose 2017-06-19 06:47:41 UTC 
Yes - 4.2
Comment 4 Sandro Bonazzola 2017-09-22 13:20:13 UTC 
Requirement changed, we need to rebase on 3.12
Comment 5 Red Hat Bugzilla Rules Engine 2017-09-22 13:20:19 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 6 Nikolai Sednev 2017-10-30 10:13:18 UTC 
Moving to verified.
Deloyment worked for me on pair of clean hosts over latest gluster 3.12.

SHE version:
ovirt-hosted-engine-setup-2.2.0-0.0.master.20171016160008.git55723e8.el7.centos.noarch
Comment 7 Sandro Bonazzola 2017-12-20 11:17:06 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.
Note You need to log in before you can comment on or make changes to this bug.