Bug 1660062 - Rest-API: Link to disk-attachments under storage-domain contains 'null'
Summary: Rest-API: Link to disk-attachments under storage-domain contains 'null'
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RestAPI
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.3.0
: ---
Assignee: Ori Liel
QA Contact: Ravi Nori
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-17 12:27 UTC by Ori Liel
Modified: 2019-02-13 07:45 UTC (History)
4 users (show)

Fixed In Version: ovirt-engine-4.3.0_rc
Clone Of:
Environment:
Last Closed: 2019-02-13 07:45:00 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-4.3+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 96426 0 master MERGED restapi: Fix link to disks under SD 2019-01-03 08:41:56 UTC

Description Ori Liel 2018-12-17 12:27:25 UTC
Description of problem:

Getting disk-attachments under storage-domain via the API returns disk-attachment objects in which the href string contains 'null', something like: ...api/storagedomains/null/diskattachments/yyy/

Steps to Reproduce:

1. Make a get request: GET ...api/storagedomains/xxx/diskattachments

Actual results:

href attributes of the disk-attachments contain 'null' instead of the ID of the storage-domain

Expected results:

Instead of null the hrefs should contain the ids of the storage-domain

Comment 2 Ori Liel 2018-12-24 08:40:44 UTC
Actually the expected results should be that the disks appear under the root of the API, because this was the behavior before: 

.../api/disks/xxx

Comment 3 Sandro Bonazzola 2019-02-13 07:45:00 UTC
This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.0 release, 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.