Bug 1539710

Summary: Selecting filter with "expression Service: Aggregate All Vm Cpus" results in exception
Product: Red Hat CloudForms Management Engine Reporter: Matouš Mojžíš <mmojzis>
Component: APIAssignee: Nick LaMuro <nlamuro>
Status: CLOSED CURRENTRELEASE QA Contact: Angelina Vasileva <anikifor>
Severity: high Docs Contact:
Priority: high    
Version: 5.9.0CC: cpelland, hkataria, lavenel, mmojzis, mpovolny, obarenbo, simaishi, yrudman
Target Milestone: GAKeywords: TestOnly
Target Release: 5.10.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: ui:filter
Fixed In Version: 5.10.0.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1540698 1540699 (view as bug list) Environment:
Last Closed: 2019-02-11 14:10:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1540698, 1540699    
Attachments:
Description Flags
production.log stacktrace
none
db dump none

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.