Bug 1654679 - Provide upgrade instructions for oVirt 4.3 which is based on Gluster 5
Summary: Provide upgrade instructions for oVirt 4.3 which is based on Gluster 5
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: vdsm
Classification: oVirt
Component: Gluster
Version: 4.20.31
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ovirt-4.3.2
: ---
Assignee: Sahina Bose
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-29 12:08 UTC by Gianluca Cecchi
Modified: 2019-03-19 10:05 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-03-19 10:05:21 UTC
oVirt Team: Gluster
Embargoed:
sbonazzo: ovirt-4.3?
sbonazzo: blocker?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?

Attachments (Terms of Use)

Description Gianluca Cecchi 2018-11-29 12:08:25 UTC 
Description of problem:
Currently on updated 4.2.7 node I have gluster 3.12.15, that is EOL as of 
https://www.gluster.org/release-schedule/


Version-Release number of selected component (if applicable):
glusterfs-3.12.15-1.el7.x86_64
glusterfs-libs-3.12.15-1.el7.x86_64
glusterfs-api-3.12.15-1.el7.x86_64
glusterfs-fuse-3.12.15-1.el7.x86_64
glusterfs-cli-3.12.15-1.el7.x86_64
glusterfs-client-xlators-3.12.15-1.el7.x86_64

vdsm-4.20.43-1.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. instal node or update to latest 4.2 repo packages
2. verify version of vdsm and gluster
3. Gluster is 3.12

Actual results:
3.12

Expected results:
4.1.5 at least

Additional info:
Comment 1 Gianluca Cecchi 2018-11-30 09:51:25 UTC 
Eg. version 4.1.5 is considered LTM as it results from this post on gluster announce mailing list: 

https://lists.gluster.org/pipermail/announce/2018-September/000113.html
Comment 2 Sahina Bose 2019-01-03 05:15:53 UTC 
(In reply to Gianluca Cecchi from comment #1)
> Eg. version 4.1.5 is considered LTM as it results from this post on gluster
> announce mailing list: 
> 
> https://lists.gluster.org/pipermail/announce/2018-September/000113.html

The reason we cannot update to Gluster >= 4.x is due to removal of gluster-nfs package that vdsm depends on. The last time we made this change, it broke the users using this feature.
With oVirt 4.3, we provide steps for nfs users to migrate and bump up the Gluster version.
Any suggestions to solve this is welcome
Comment 3 Sandro Bonazzola 2019-02-14 14:12:53 UTC 
Converting this to documentation bug for 4.3 since it has been already released and we need clear instructions for the upgrade flow with gluster.
Giving up on 4.2 since it has reached EOL with 4.3 release.
Comment 5 Gobinda Das 2019-02-27 10:56:00 UTC 
Ovirt-4.3.1 already released, so moving to ovirt-4.3.2
Comment 6 Sahina Bose 2019-03-04 10:59:54 UTC 
The gluster-gnfs dependency issues is resolved with gluster version 5.3-2 and above
Comment 7 SATHEESARAN 2019-03-12 17:34:02 UTC 
Verified that the gnfs dependency is removed
Comment 8 Sandro Bonazzola 2019-03-19 10:05:21 UTC 
This bugzilla is included in oVirt 4.3.2 release, published on March 19th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.2 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.
Note You need to log in before you can comment on or make changes to this bug.