Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1518558

Summary:	Disable gfapi access for 4.2 cluster
Product:	[oVirt] ovirt-engine	Reporter:	Sahina Bose <sabose>
Component:	BLL.Gluster	Assignee:	Sahina Bose <sabose>
Status:	CLOSED CURRENTRELEASE	QA Contact:	SATHEESARAN <sasundar>
Severity:	medium	Docs Contact:
Priority:	high
Version:	4.2.0	CC:	bugs, ratamir
Target Milestone:	ovirt-4.2.0	Flags:	rule-engine: ovirt-4.2+ rule-engine: blocker+ rule-engine: planning_ack+ rule-engine: devel_ack+ sasundar: testing_ack+
Target Release:	4.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.2.0	Doc Type:	Bug Fix
Doc Text:	Cause: gfapi access is enabled by default on 4.2 clusters Consequence: Live storage migration and HA when primary gluster storage server is down, does not work with gfapi access Fix: Disable gfapi access for 4.2 cluster	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-10 06:31:02 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:

Description Sahina Bose 2017-11-29 08:13:37 UTC

Description of problem:

Currently gfapi access is enabled for 4.2 clusters, but with gfapi access live storage migration and HA is not available.
Hence disabling this till these issues are fixed

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

How reproducible:
NA

Comment 1 Allon Mureinik 2017-11-30 12:42:36 UTC

*** Bug 1519149 has been marked as a duplicate of this bug. ***

Comment 2 SATHEESARAN 2018-05-06 18:04:59 UTC

Verified with RHV 4.2.3, gfapi is not enabled by default on the cluster

Comment 3 Sandro Bonazzola 2018-05-10 06:31:02 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.