Bug 1528283 - Add the ability to search storage domains by their Discard After Delete value in the webadmin
Summary: Add the ability to search storage domains by their Discard After Delete value...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Search-Backend
Version: future
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ovirt-4.2.1
: ---
Assignee: Idan Shaby
QA Contact: Lucie Leistnerova
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-21 12:45 UTC by Idan Shaby
Modified: 2018-02-12 11:57 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-02-12 11:57:53 UTC
oVirt Team: Storage
Embargoed:
rule-engine: ovirt-4.2+
rule-engine: ovirt-4.3+
lsvaty: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 85672 0 master MERGED searchbackend: search storage domains by Discard After Delete 2017-12-24 16:54:24 UTC

Description Idan Shaby 2017-12-21 12:45:22 UTC 
Description of problem:
The ability to search storage domains by their Discard After Delete value in the webadmin is missing.

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

How reproducible:
100%

Steps to Reproduce:
1. Navigate to the storage domains tab in the webadmin.
2. In the search box, type: "discard_after_delete".

Actual results:
Nothing happens because there is no option to filter the results by the Discard After Delete value.
Comment 1 Lucie Leistnerova 2018-01-17 13:59:41 UTC 
discard_after_delete offered by auto-completion and search works

verified in ovirt-engine-4.2.1.1-0.1.el7.noarch
Comment 2 Sandro Bonazzola 2018-02-12 11:57:53 UTC 
This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.1 release, 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.