Bug 2027272 - KubeMemoryOvercommit alert should be human readable
Summary: KubeMemoryOvercommit alert should be human readable
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.0
Assignee: Philip Gough
QA Contact: Junqi Zhao
Depends On:
TreeView+ depends on / blocked
Reported: 2021-11-29 09:49 UTC by Vadim Rutkovsky
Modified: 2022-03-10 16:30 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-03-10 16:30:41 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github kubernetes-monitoring kubernetes-mixin pull 717 0 None Merged alerts: Humanize KubeMemoryOvercommit byte value 2021-12-01 10:22:27 UTC
Github openshift cluster-monitoring-operator pull 1506 0 None open Bug 2027272: Humanize bytes value for KubeMemoryOvercommit 2021-12-06 14:21:08 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:30:57 UTC

Description Vadim Rutkovsky 2021-11-29 09:49:30 UTC
Description of problem:
KubeMemoryOvercommit alert description contains bytes:
Cluster has overcommitted memory resource requests for Pods by 2.278214144e+09 bytes and cannot tolerate node failure.
which is not human readable. Alert text should use `{{ $value | humanize1024 }}` for readability

Comment 2 Junqi Zhao 2021-12-08 09:51:40 UTC
tested with PR, the value is humanized, example:
alert description now is
Cluster has overcommitted memory resource requests for Pods by 76.45G bytes and cannot tolerate node failure.

Comment 9 errata-xmlrpc 2022-03-10 16:30:41 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 (Moderate: OpenShift Container Platform 4.10.3 security update), 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.