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

Bug 1347157

Summary:	[v4] capabilities was removed
Product:	[oVirt] ovirt-engine	Reporter:	Nelly Credi <ncredi>
Component:	RestAPI	Assignee:	Juan Hernández <juan.hernandez>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.0.0	CC:	bugs, grafuls, mperina, trichard
Target Milestone:	ovirt-4.0.1	Keywords:	Automation
Target Release:	4.0.1.1	Flags:	rule-engine: ovirt-4.0.z+ rule-engine: planning_ack+ juan.hernandez: devel_ack+ rule-engine: testing_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	In version 4 of the API, the top level /capabilities collection has been replaced with /clusterlevels, which contains information about the supported cluster levels (such as the available CPU types). The legal values for enumerated types, previously found in /capabilities, can now be found in /ovirt-engine/api/model.xml or /ovirt-engine/api/model.json.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-19 06:24:18 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 Nelly Credi 2016-06-16 07:52:49 UTC

Description of problem:
capabilities have been removed in v4.
we need it

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


How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
it is agreed with Juan to add it back under the name 'cluster_levels'
with versions under it and all the relevant information

Comment 1 Nelly Credi 2016-07-14 13:37:56 UTC

we are still missing permits, but there is a different bug for it
https://bugzilla.redhat.com/show_bug.cgi?id=1355647

Comment 2 Sandro Bonazzola 2016-07-19 06:24:18 UTC

Since the problem described in this bug report should be
resolved in oVirt 4.0.1 released on July 19th 2016, it has been closed with a
resolution of CURRENT RELEASE.

For information on the release, and how to update to this release, follow the link below.

If the solution does not work for you, open a new bug report.

http://www.ovirt.org/release/4.0.1/

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

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