Memory leaks when using OpenSCAP
|Assigned To:||Ondřej Pražák|
|Target version:||Foreman - Team Marek backlog|
|Found in release:||Pull request:||https://github.com/theforeman/smart_proxy_openscap/pull/47|
|Velocity based estimate||-|
|Release||smart_proxy_openscap 0.6.3||Release relationship||Auto|
Description of problem:
A user is noticing that foreman-proxy is dying and we suspected it was due to the large amount of clients being checked by the OpenSCAP plugin. I tried to reproduce locally and saw the same issue.
Steps to Reproduce:
1. Set up a system with one host, an OpenSCAP policy and attach the policy to the host.
2. Set OpenSCAP to scan the host every minute
Memory usage balloons until the OOM killer terminates foreman-proxy
Memory usage remains relatively constant.
#3 Updated by Ondřej Pražák 10 months ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset smart_proxy_openscap|4adace544b37790456451e316d2a71387708d1ab.