Bug 1377332 - [REST] Capabilities entry point missing
Summary: [REST] Capabilities entry point missing
Keywords:
Status: CLOSED DUPLICATE of bug 1347157
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 4.0.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Juan Hernández
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-19 13:00 UTC by Gonza
Modified: 2016-09-20 07:35 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-20 07:35:05 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.