Fedora Account System
Red Hat Associate
Red Hat Customer
Created attachment 1412350 [details] evmlog Description of problem: Reporting worker exceeding memory threshold. Default report Provisional Activity -by VM attached to custom widget: Provisioning Activity - Provider Info Memory threshold set for 1.5 GB, memory is exceeding to 4 GB when populating the widget. Version-Release number of selected component (if applicable): 5.8.2.3 How reproducible: Always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Hello Taun, Can we get a copy of the report.yml for "Default report Provisional Activity -by VM" And the dashboard widget: "Provisioning Activity - Provider Info" Also, do we have a database backup for this customer? Hard for me to diagnose without seeing the columns for the report, or the data. If there are no date fields in the report.yml, they may want to take advantage of a widget option that reduces the number of report permutations that are generated: In the widget.yml file: options: :timezone_matters: false Please send across the report.yml, widget.yml, and see if you can get a customer dump. Thanks, Keenan
Taun, Still looking into this. Looking to speed up the report by default Keenan
https://github.com/ManageIQ/manageiq/pull/17246
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/fc5a68cf74b019ad833c2b301b323a23db77a32a commit fc5a68cf74b019ad833c2b301b323a23db77a32a Author: Keenan Brock <keenan> AuthorDate: Mon Apr 2 15:04:15 2018 -0400 Commit: Keenan Brock <keenan> CommitDate: Mon Apr 2 15:04:15 2018 -0400 convert Vm#miq_provision_template to has_one Provision Activity report uses this field in a where clause This change allows the report to run without downloading all data https://bugzilla.redhat.com/show_bug.cgi?id=1560113 app/models/vm_or_template.rb | 6 +- spec/models/vm_or_template_spec.rb | 26 + 2 files changed, 27 insertions(+), 5 deletions(-)
part of today's build
Hi, After looking at the referenced BZs 1556526 and 1566528, it seems like QE doesn't have an environment to test this bug. See : https://bugzilla.redhat.com/show_bug.cgi?id=1566526#c9. Thanks, Parthvi
https://bugzilla.redhat.com/show_bug.cgi?id=1566526#c9