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

Bug 1377332

Summary:	[REST] Capabilities entry point missing
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Gonza <grafuls>
Component:	ovirt-engine	Assignee:	Juan Hernández <juan.hernandez>
Status:	CLOSED DUPLICATE	QA Contact:	meital avital <mavital>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.0.3	CC:	gklein, lsurette, mperina, rbalakri, Rhev-m-bugs, srevivo, ykaul
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-09-20 07:35:05 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Gonza 2016-09-19 13:00:47 UTC

Description of problem:
We need the ability to list available permits from the API which on v3 we could find under the capabilities entry point which is no longer there on v4.
This seems to be a regression since it was previously fixed under BZ1355647

Version-Release number of selected component (if applicable):
ovirt-engine-restapi-4.0.4.3-0.1.el7ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. Go to https://{engine}/ovirt-engine/api/capabilities

Actual results:
No results are returned

Expected results:
Results for capabilities are returned

Comment 1 Juan Hernández 2016-09-20 07:35:05 UTC

The 'capabilities' collection has been removed in version 4 of the API. It has been replaced by the new 'clusterlevels' collection. See here for details:

  https://github.com/oVirt/ovirt-engine/blob/master/backend/manager/modules/restapi/README.adoc#39-removed-the-capabilitiespermits-element

The new 'clusterlevels' collection was added by this patch:

  restapi: Add cluster levels support
  https://gerrit.ovirt.org/59227

This was done in order to fix bug 1347157, and was included in version 4.0.1.1 of the engine. I'm closing this bug as a duplicate.

*** This bug has been marked as a duplicate of bug 1347157 ***