Description of problem: Currently V4 API still supports V3 lists and actions on VM disks in: api/vms/{vm_id}/disks api/vms/{vm_id}/disks/{disk_id} Those should be removed and the functionality should only be supported in: api/vms/{vm_id}/diskattachments api/vms/{vm_id}/diskattachments/{disk_attachment_id} The functionality in V4 resources used by delegation from V3 should be moved to V3 classes Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
This kind of change can't be targeted to 4.0.1, as we are not allowed to make backwards compatibility breaking changes once version 4 of the API is released. Please retarget to 4.0.0, or close as WONTFIX.
We will have a release note on removal of this. We should allow small changes in the first z streams of the 4.0 API.
We don't have many users that already moved to v4 of the API therefore we can allow small breakages of backwards compatibility on a case by case request. This one is approved.
Tal - this should be documented. Not sure if here or as part of a broader API documentation.
Verified on rhevm-4.0.1.1-0.1.el7ev.noarch. There is no link to api/vms/{vm_id}/disks with v4 api
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/