Bug 1537132
Summary: | Miq Server leaks memory and we fail to detect and remediate it | ||
---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | Satoe Imaishi <simaishi> |
Component: | Appliance | Assignee: | Joe Rafaniello <jrafanie> |
Status: | CLOSED ERRATA | QA Contact: | Tasos Papaioannou <tpapaioa> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 5.8.0 | CC: | abellott, cpelland, jrafanie, obarenbo, simaishi, tpapaioa |
Target Milestone: | GA | Keywords: | ZStream |
Target Release: | 5.8.4 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | 5.8.4.1 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1533484 | Environment: | |
Last Closed: | 2018-06-25 14:17:13 UTC | Type: | --- |
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: | 1533484 | ||
Bug Blocks: |
Comment 1
Joe Rafaniello
2018-02-23 20:06:53 UTC
New commit detected on ManageIQ/manageiq/fine: https://github.com/ManageIQ/manageiq/commit/ac5415750afe2fe2ee180beae4027fe3f0f4dc5b commit ac5415750afe2fe2ee180beae4027fe3f0f4dc5b Author: Nick Carboni <ncarboni> AuthorDate: Fri Jan 12 09:01:15 2018 -0500 Commit: Satoe Imaishi <simaishi> CommitDate: Thu Mar 1 16:21:38 2018 -0500 Merge pull request #16807 from jrafanie/exit_server_on_large_memory_usage Server shuts down if memory usage exceeds a limit (cherry picked from commit 39dfff4a5a9e8ee6f6b0d61ea945cdadb856620d) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1537132 app/models/miq_server.rb | 21 +++++++++++++++++++++ config/settings.yml | 1 + db/fixtures/notification_types.yml | 5 +++++ spec/models/miq_server_spec.rb | 24 ++++++++++++++++++++++++ 4 files changed, 51 insertions(+) Verified on 5.8.4.2. 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/RHSA-2018:1972 |