Bug 1444052 - Chargeback report generation keeps whole openshift env in the memory (even after it finishes)
Summary: Chargeback report generation keeps whole openshift env in the memory (even af...
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Reporting
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: GA
: 5.7.3
Assignee: Šimon Lukašík
QA Contact: Einat Pacifici
Depends On: 1443606
TreeView+ depends on / blocked
Reported: 2017-04-20 13:31 UTC by Satoe Imaishi
Modified: 2017-06-28 15:00 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1443606
Last Closed: 2017-06-28 15:00:50 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:1601 0 normal SHIPPED_LIVE Important: CFME 5.7.3 security, bug fix and enhancement update 2017-06-28 18:51:52 UTC

Comment 2 CFME Bot 2017-04-26 18:15:49 UTC
New commit detected on ManageIQ/manageiq/euwe:

commit 1ea01612ba7b446caeaf43087565eacd851a6536
Author:     Gregg Tanzillo <gtanzill@redhat.com>
AuthorDate: Thu Apr 20 10:19:27 2017 +0200
Commit:     Satoe Imaishi <simaishi@redhat.com>
CommitDate: Wed Apr 26 14:11:31 2017 -0400

    Merge pull request #14807 from isimluk/cb-container-performance-memory
    Do not store whole container env. in the reporting worker forever
    (cherry picked from commit 45ac9b673d289df65515a257804672233a2d57ac)

 app/models/chargeback_container_image.rb   | 2 ++
 app/models/chargeback_container_project.rb | 2 ++
 2 files changed, 4 insertions(+)

Comment 5 errata-xmlrpc 2017-06-28 15:00:50 UTC
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.


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