Bug 1601873 - Remove dependency on gluster-gnfs to support Gluster 4.1
Summary: Remove dependency on gluster-gnfs to support Gluster 4.1
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: vdsm
Classification: oVirt
Component: Gluster
Version: 4.30.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-4.3.0
: 4.30.3
Assignee: Sahina Bose
QA Contact: SATHEESARAN
Rolfe Dlugy-Hegwer
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-17 11:44 UTC by Parth Dhanjal
Modified: 2019-03-13 16:37 UTC (History)
8 users (show)

Fixed In Version: v4.30.3
Doc Type: Removed functionality
Doc Text:
In this release, gluster-gnfs is no longer available with Gluster 4.1. Users who require nfs access for gluster volumes are advised to use nfs-ganesha. Please refer to https://gluster.readthedocs.io/en/latest/Administrator%20Guide/NFS-Ganesha%20GlusterFS%20Integration/
Clone Of:
Environment:
Last Closed: 2019-03-13 16:37:45 UTC
oVirt Team: Gluster
Embargoed:
rule-engine: ovirt-4.3+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 94060 0 master MERGED gluster: Removing glusterfs-gnfs dependency 2018-09-19 14:47:33 UTC

Description Parth Dhanjal 2018-07-17 11:44:14 UTC 
Description of problem:
Can't install VDSM on the host because of missing dependency in gluster-4.1 repo.

Version-Release number of selected component (if applicable):
gluster-4.1

How reproducible:
Always

Steps to Reproduce:
1. Try installing vdsm-4.3 along with gluster-4.1 repo.
Comment 1 Sahina Bose 2018-07-17 14:26:50 UTC 
Also need to provide existing gnfs users a migration path to nfs-ganesha.
Comment 2 Sahina Bose 2018-09-03 12:33:52 UTC 
Can you review the doc text?
Comment 3 Jiffin 2018-09-04 09:26:38 UTC 
Look goods to me
Comment 4 SATHEESARAN 2019-03-12 17:13:07 UTC 
Verified with oVirt-4.3 and glusterfs-3.12.2
Comment 5 Sandro Bonazzola 2019-03-13 16:37:45 UTC 
This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.0 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.