Bug 1539710 - Selecting filter with "expression Service: Aggregate All Vm Cpus" results in exception
Summary: Selecting filter with "expression Service: Aggregate All Vm Cpus" results in ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: API
Version: 5.9.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.10.0
Assignee: Nick LaMuro
QA Contact: Angelina Vasileva
URL:
Whiteboard: ui:filter
Depends On:
Blocks: 1540698 1540699
TreeView+ depends on / blocked
 
Reported: 2018-01-29 13:45 UTC by Matouš Mojžíš
Modified: 2019-08-22 00:55 UTC (History)
8 users (show)

Fixed In Version: 5.10.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1540698 1540699 (view as bug list)
Environment:
Last Closed: 2019-02-11 14:10:08 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
production.log stacktrace (6.30 KB, text/plain)
2018-01-29 13:45 UTC, Matouš Mojžíš
no flags Details
db dump (7.67 MB, application/octet-stream)
2018-01-29 20:35 UTC, Yuri Rudman
no flags Details

Description Matouš Mojžíš 2018-01-29 13:45:04 UTC
Created attachment 1387799 [details]
production.log stacktrace

Description of problem:


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

How reproducible:
Always

Steps to Reproduce:
1. Go to Services -> My Services
2. Create filter with expression: Service: Aggregate All Vm Cpus  = 454
3.

Actual results:
Exception appears

Expected results:


Additional info:

Comment 2 Yuri Rudman 2018-01-29 17:10:33 UTC
I can not recreate reported issue.
Is it possible to have access to appliance where we can recreate or attach db dump ?

Comment 4 Yuri Rudman 2018-01-29 20:35:46 UTC
Created attachment 1388032 [details]
db dump

Comment 5 Nick LaMuro 2018-01-31 02:29:51 UTC
So a proposed solution is here:

https://github.com/ManageIQ/manageiq/pull/16915

This effectively removes the filtering via SQL for these columns, but as explain in the pull request, it is ideal since the poor performance this can cause on index actions is far worse for the appliance then a N+1 based filter.

The solution to make it work for both is far more involved, and arguably not worth it.


* * *

Of note, this is an issue in versions all the way back to 5.6 (darga), since the changes to these columns was introduced and backported in this patch:

https://github.com/ManageIQ/manageiq/pull/11502

Causing the issues in this BZ.

Comment 8 Matouš Mojžíš 2018-07-10 13:19:35 UTC
Verified in 5.10.0.3. This filter works now.


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