Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1453159

Summary: Allow filtering of disks according to their content type in webadmin
Product: [oVirt] ovirt-engine Reporter: Tal Nisan <tnisan>
Component: BLL.StorageAssignee: Tal Nisan <tnisan>
Status: CLOSED CURRENTRELEASE QA Contact: Raz Tamir <ratamir>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: amureini, bugs
Target Milestone: ovirt-4.2.0Flags: rule-engine: ovirt-4.2+
Target Release: ---   
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: 2017-12-20 10:47:21 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:
Bug Depends On: 1452989    
Bug Blocks:    
Attachments:
Description Flags
screenshot none

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.