Bug 1528294
Summary: | Webadmin's disk search throws an exception when trying to filter by the "bootable" property | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Idan Shaby <ishaby> |
Component: | Search-Backend | Assignee: | Tal Nisan <tnisan> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Lucie Leistnerova <lleistne> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | future | CC: | bugs, emesika, lsvaty, tnisan |
Target Milestone: | ovirt-4.2.1 | Flags: | rule-engine:
ovirt-4.2+
lsvaty: testing_ack+ |
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: | 2018-02-12 11:48:37 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: |
Description
Idan Shaby
2017-12-21 13:24:14 UTC
It seems that the search configuration for this query is wrong , there is no "boot" flag in all disks view ... There is a is_boot flag in table_name | column_name -------------------------------------+----------------------- disk_vm_element | is_boot disk_vm_element_extended | is_boot This might be related .... Right, it was moved to disk_vm_element a while ago. Since we don't support searching in this table yet (Bug 1528293), the solution should be to remove the boot flag for now. bootable is not offered by the auto-completion and search doesn't generate any error, also no items in result verified in ovirt-engine-4.2.1.1-0.1.el7.noarch 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. |