Hide Forgot
Description of problem: Depending on the size of reports for a host, the request for the reports for a host via API/hammer consumes large amount of memory. How reproducible: the system needs to have reasonable history of puppet reports in order to reporduce the issue Steps to Reproduce: 1. curl -k -u admin:changeme -H "Accept:application/json"\ https://foreman.example.com/api/v2/hosts/myhost.example.com/reports?per_page=120 Actual results: The passenger process starts consuming a lot of memory and it takes tens of minuts to finish (if the server doesn't fail on insufficient amount of memory before it finishes). Expected results: The request returns reports for a host
Created redmine issue http://projects.theforeman.org/issues/14503 from this bug
A PR with a fix proposal opened upstream https://github.com/theforeman/foreman/pull/3394
Upstream bug component is Provisioning
Moving to POST since upstream bug http://projects.theforeman.org/issues/14503 has been closed ------------- Ivan Necas Applied in changeset commit:aeba4f428494f2ee3aedf18088561c23c4407309.
Verified in Satellite 6.2 Beta Snap 13. It only took 1120ms to return a list of 345 reports, when overriding the default pagination limits.
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. https://access.redhat.com/errata/RHBA-2016:1501