Bug 1454389

Summary:	[RFE] add search query for cluster compatibility level override
Product:	[oVirt] ovirt-engine	Reporter:	Shmuel Melamud <smelamud>
Component:	Frontend.WebAdmin	Assignee:	Andrej Krejcir <akrejcir>
Status:	CLOSED CURRENTRELEASE	QA Contact:	samuel macko <smacko>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	future	CC:	akrejcir, apinnick, aromito, bugs, rbarry
Target Milestone:	ovirt-4.3.0	Keywords:	FutureFeature
Target Release:	---	Flags:	rbarry: ovirt-4.3? lleistne: testing_plan_complete+ rule-engine: planning_ack? rule-engine: devel_ack+ lsvaty: testing_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.3.0_rc	Doc Type:	Enhancement
Doc Text:	The current release of the Administration Portal supports search queries for virtual machines with a specific cluster compatibility override setting or with a different cluster compatibility override setting (or none): `Vms: custom_compatibility_level = X.Y` or `!= X.Y`.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-02-21 14:17:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1454821
Bug Blocks:

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. ***