Bug 1518558 - Disable gfapi access for 4.2 cluster
Summary: Disable gfapi access for 4.2 cluster
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Gluster
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ovirt-4.2.0
: 4.2.0
Assignee: Sahina Bose
QA Contact: SATHEESARAN
URL:
Whiteboard:
: 1519149 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-29 08:13 UTC by Sahina Bose
Modified: 2018-05-10 06:31 UTC (History)
2 users (show)

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
Clone Of:
Environment:
Last Closed: 2018-05-10 06:31:02 UTC
oVirt Team: Gluster
Embargoed:
rule-engine: ovirt-4.2+
rule-engine: blocker+
rule-engine: planning_ack+
rule-engine: devel_ack+
sasundar: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 84844 0 master MERGED core: Default gfapi access support to false 2021-02-19 15:48:21 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.