Bug 1513398
| Summary: | rhv manager does not show the results of the search properly | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Marian Jankular <mjankula> | |
| Component: | ovirt-engine | Assignee: | Eli Mesika <emesika> | |
| Status: | CLOSED ERRATA | QA Contact: | Lucie Leistnerova <lleistne> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | high | |||
| Version: | 4.1.6 | CC: | apinnick, inetkach, lsurette, lsvaty, lveyde, mgoldboi, mjankula, mperina, obockows, pmatyas, pstehlik, Rhev-m-bugs, sborella, srevivo, tjelinek | |
| Target Milestone: | ovirt-4.3.0 | Keywords: | ZStream | |
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | ovirt-engine-4.3.0_rc | Doc Type: | If docs needed, set a value | |
| Doc Text: |
In the Administration Portal, searching for virtual machines by network label, VM emulated machine, and CPU type are not supported due to the complexity of their implementation.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1519777 (view as bug list) | Environment: |
It should be documented that network label and vm emulated machine and cpu type are not supported due to complexity of implementation
|
|
| Last Closed: | 2019-05-08 12:36:48 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1519777 | |||
|
Description
Marian Jankular
2017-11-15 10:42:24 UTC
It is an issue in BaseConditionFieldAutoCompleter. There were some fixes around this area in 4.2 but Im not sure it will handle also this case: https://bugzilla.redhat.com/show_bug.cgi?id=1252906 https://bugzilla.redhat.com/show_bug.cgi?id=1454821 Moving to infra to make sure. When searching for "Vms: comment != foo" I get only VM2 (using example in description). Not sure if this was intended, but from description it appears that it is desired by reporter. Tested on ovirt-engine-4.2.2.1-0.1.el7.noarch INFO: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [Tag 'ovirt-engine-4.2.2.4' doesn't contain patch 'https://gerrit.ovirt.org/87560'] gitweb: https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=shortlog;h=refs/tags/ovirt-engine-4.2.2.4 For more info please contact: rhv-devops Verified on ovirt-engine-4.2.2.4-0.1.el7.noarch reopening this bug. The reason is that BZ 1519777 on 4.1 failed verification. When I checked that, I found that verification on upgraded system will succeed (as done on master/4.2) while verification on new system will fail (as in 4.1) The reason for that is that even if we change the default to be empty string, if we pass NULL explicitly for the column value (as our SP do when called from DAO code) , then NULL is inserted into the database and the BZ is reproduced. I have consulted with Martin and we concluded that we will: 1) Reopen this BZ 2) Change the corresponding columns in database to be NOT NULL 3) Change the corresponding business entities field setters to set the value to empty string if it is null 4) Back-port the fix to 4.2 and 4.1 branch NOTE: 1) This should be tested on new entities added to the application. 2) The solution does not include cluster table cpu_name and emulated_machine columns that fails on empty string value on OST. Fixing this issue is much more problematic then we though, moving to 4.3 and once fixed properly we can think of 4.2.z backport Leftovers which are still not working :
> Storage.description
> Storage.comment
> Disk.description
Search for description/comment works as expected. I've tried it on new installation and also on upgraded 4.1 -> 4.2 -> 4.3 verified in ovirt-engine-4.3.0-0.8.rc2.el7.noarch Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:1085 |