Bug 1528293

Summary:	[RFE] Add the webadmin's disks' search the ability to filter disks by their VM related properties
Product:	[oVirt] ovirt-engine	Reporter:	Idan Shaby <ishaby>
Component:	Search-Backend	Assignee:	Idan Shaby <ishaby>
Status:	CLOSED WONTFIX	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	future	CC:	bugs, dfediuck, tnisan, ylavi
Target Milestone:	---	Keywords:	FutureFeature, Improvement
Target Release:	---	Flags:	ylavi: ovirt-future? rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack?
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-29 13:25:29 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Idan Shaby 2017-12-21 13:24:06 UTC

Description of problem:
Today, the webadmin's search tool is able to filter a disk by some disk's properties, but not by the properties that are unique to the relation of the disk to its VM. For example: bootable, pass discard, interface etc.

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

How reproducible:
100%

Comment 1 Red Hat Bugzilla Rules Engine 2018-01-08 16:15:49 UTC

This request has been proposed for two releases. This is invalid flag usage. The ovirt-future release flag has been cleared. If you wish to change the release flag, you must clear one release flag and then set the other release flag to ?.

Comment 2 Yaniv Kaul 2018-03-01 13:09:38 UTC

Allon, do we have any plans to implement this in 4.3?
If not, I suggest deferring.

Comment 3 Allon Mureinik 2018-03-04 10:33:49 UTC

(In reply to Yaniv Kaul from comment #2)
> Allon, do we have any plans to implement this in 4.3?
> If not, I suggest deferring.

Medium priority, best effort based.
This is somewhat of regression caused by moving out the bootable property to its rightful location.

Comment 4 Doron Fediuck 2018-05-29 13:25:29 UTC

Closing older RFEs.
If relevant, please re-open and explain why.
As always, patches are welcomed!

Comment 5 Idan Shaby 2018-05-30 04:59:03 UTC

It's not so old :)
Tal - don't we want to implement it?
A part of it is a regression (bootable) and the other part is missing functionality (Enable Discard, Interface etc.).

Comment 6 Tal Nisan 2018-05-30 08:03:04 UTC

It will require adding another join to the disks search (to disk_vm_element) which will introduce a performance hit in environments with many disks (most production environments), since no customer opened a ticket for that I assume that this functionality was not really used so we can close this bug