Bug 1453159 - Allow filtering of disks according to their content type in webadmin
Summary: Allow filtering of disks according to their content type in webadmin
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Storage
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.2.0
: ---
Assignee: Tal Nisan
QA Contact: Raz Tamir
URL:
Whiteboard:
Depends On: 1452989
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-22 09:41 UTC by Tal Nisan
Modified: 2017-12-20 10:47 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-12-20 10:47:21 UTC
oVirt Team: Storage
Embargoed:
rule-engine: ovirt-4.2+

Attachments (Terms of Use)
screenshot (39.93 KB, image/png)
2017-08-22 06:15 UTC, Raz Tamir 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 80242 0 master MERGED webadmin: Allow filtering disks by content type 2017-08-15 15:53:36 UTC

Description Tal Nisan 2017-05-22 09:41:54 UTC 
Description of problem:
Allow filtering of the disks in the main disks tab according to their content type similar to the filtering by storage type (Images/LUNs/Cinder/All).
The default should should only data disks and filter out OVF disks and memory images
Comment 1 Raz Tamir 2017-08-22 06:15:28 UTC 
Verified on 4.2.0-0.0.master.20170820180837.git59243e9.el7.centos

screenshot attached
Comment 2 Raz Tamir 2017-08-22 06:15:50 UTC 
Created attachment 1316528 [details]
screenshot
Comment 3 Allon Mureinik 2017-09-14 16:31:12 UTC 
Tal, can you please provide some doctext on this?
Comment 4 Red Hat Bugzilla Rules Engine 2017-11-21 09:13:13 UTC 
The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again.
Comment 5 Sandro Bonazzola 2017-12-20 10:47:21 UTC 
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, 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.