Bug 1454389 - [RFE] add search query for cluster compatibility level override
Summary: [RFE] add search query for cluster compatibility level override
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: future
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.3.0
: ---
Assignee: Andrej Krejcir
QA Contact: samuel macko
URL:
Whiteboard:
: 1758565 (view as bug list)
Depends On: 1454821
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-22 15:22 UTC by Shmuel Melamud
Modified: 2019-10-09 10:52 UTC (History)
5 users (show)

Fixed In Version: ovirt-engine-4.3.0_rc
Clone Of:
Environment:
Last Closed: 2019-02-21 14:17:13 UTC
oVirt Team: Virt
Embargoed:
rbarry: ovirt-4.3?
lleistne: testing_plan_complete+
rule-engine: planning_ack?
rule-engine: devel_ack+
lsvaty: testing_ack+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 95442 0 master MERGED search: Add search query for VM custom compatibility level 2020-12-09 21:18:51 UTC
oVirt gerrit 95747 0 master MERGED search: Queries with != operator return objects with null parameter 2020-12-09 21:18:51 UTC

Description Shmuel Melamud 2017-05-22 15:22:02 UTC
Add search query in Web UI to look for VMs by cluster compatibility level override (custom_compatibility_version field in "vms" view).

Additional info:

In draft implementation, when we write a search query:

Vms: custom_compatibility_level = 4.1

it is translated into SQL:

select ... where custom_compatibility_version IS NULL OR custom_compatibility_version = '4.1';

which is not what we want.

This is a standard translation for all string expressions, so we need to fix the parser to generate a correct SQL just in this case:

select ... where custom_compatibility_version = '4.1';

Comment 1 samuel macko 2019-02-13 13:33:03 UTC
Verified on ovirt-engine-4.3.0.4-0.1.el7.noarch.

Comment 2 Sandro Bonazzola 2019-02-21 14:17:13 UTC
This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019.

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

Comment 3 Andrej Krejcir 2019-10-09 10:52:49 UTC
*** Bug 1758565 has been marked as a duplicate of this bug. ***


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