Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1741104 - Create a specific signature for each flow in the 'Remove' REST-API interface for StorageDomainTemplate/Vm and AttachedStorageDomainDisk
Summary: Create a specific signature for each flow in the 'Remove' REST-API interface ...
Keywords:
Status: NEW
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Storage
Version: 4.3.2
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ovirt-4.5.0
: ---
Assignee: Tal Nisan
QA Contact: Avihai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-14 09:35 UTC by Eyal Shenitzky
Modified: 2020-08-04 10:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
oVirt Team: Storage
pm-rhel: ovirt-4.5?
mtessun: planning_ack+


Attachments (Terms of Use)

Description Eyal Shenitzky 2019-08-14 09:35:01 UTC
Description of problem:

Currently, the path for removing an entity (VM / Template) is the same path as removing an entity which resides on an export domain.
So before removing the entity, we should decide whether that entity is an unregistered entity or not.

In order to decide whether the entity is unregistered or not a query sent to the backend, to avoid that query we should split the path for unregistered entities or have a specific signature for each flow in the 'Remove' interface


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Tal Nisan 2019-08-19 14:12:55 UTC
Eyal, changing the path is basically breaking the current API behavior, something we should not do, what do you suggest?

Comment 2 Eyal Shenitzky 2019-08-20 07:01:57 UTC
So I think it will be better to go on the second option to overload the 'remove' interface so it will distinct between unregistered entity remove and exported VM removal.


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