Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1603399 - [RFE]- Remove the actions links from the response body when sending GET request for an unregistered floating disk
Summary: [RFE]- Remove the actions links from the response body when sending GET reque...
Keywords:
Status: POST
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RFEs
Version: 4.2.4.5
Hardware: x86_64
OS: Unspecified
unspecified
low vote
Target Milestone: ovirt-4.3.4
: ---
Assignee: Fred Rolland
QA Contact: Elad
URL:
Whiteboard:
: 1599376 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-19 14:43 UTC by Shir Fishbain
Modified: 2019-03-18 11:47 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
oVirt Team: Storage
rule-engine: ovirt-4.3?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
oVirt gerrit 95729 master POST restapi: remove actions for unregistered disks 2018-11-27 09:42:59 UTC

Description Shir Fishbain 2018-07-19 14:43:18 UTC
Description of problem:
GET request for an unregistered floating disk via REST API returns the actions links.
It's not possible to execute actions links through rest API on unregistered floating disk. So the actions shouldn't be shown in the response body.

Steps to Reproduce:
1.GET for the unregistered disks in REST API
For example: engine_address/ovirt-engine/api/storagedomains/%storage_domain%/disks?unregistered

Actual results:
Actions appear in the response for an unregistered disk.

Expected Result: 
Actions don't appear in the response for an unregistered disk.

Additional info:

Comment 1 shani 2018-07-22 09:27:30 UTC
*** Bug 1599376 has been marked as a duplicate of this bug. ***

Comment 2 Sandro Bonazzola 2019-01-28 09:40:08 UTC
This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.


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