Bug 1886907 - Flood stage wateremark alert: Remove wording that read-only index block is auto-released
Summary: Flood stage wateremark alert: Remove wording that read-only index block is au...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 4.6
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.7.0
Assignee: Lukas Vlcek
QA Contact: Qiaoling Tang
URL:
Whiteboard: logging-exploration
Depends On:
Blocks: 1888098
TreeView+ depends on / blocked
 
Reported: 2020-10-09 17:55 UTC by Lukas Vlcek
Modified: 2021-02-24 11:22 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-24 11:21:19 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift elasticsearch-operator pull 526 0 None closed Bug 1886907: Flood stage watermark alert: Remove wording that read-only index block is auto-released 2021-02-17 06:55:42 UTC
Red Hat Product Errata RHBA-2021:0652 0 None None None 2021-02-24 11:22:11 UTC

Description Lukas Vlcek 2020-10-09 17:55:22 UTC 
Description of problem:

In Elasticsearch prometheus alerts we state for the Flood ElasticsearchNodeDiskWatermarkReached alert that:
"The index block is automatically released when the disk utilization falls below the high watermark."

See:
https://github.com/openshift/elasticsearch-operator/blob/00db8da80dcbd2ae3f746b42d6a3d6492259f009/files/prometheus_alerts.yml#L71

This is not valid. See Elasticsearch PR that explains documentation change including ES versions this apply to: https://github.com/elastic/elasticsearch/pull/62627

Version-Release number of selected component (if applicable):

4.6
Comment 2 Qiaoling Tang 2020-10-15 02:58:41 UTC 
Verified with quay.io/openshift/origin-elasticsearch-operator@sha256:7cc642127d98d7e63baa5a7ae61a31c87e27f16c8bf0f84387852eb9032e526c
Comment 7 errata-xmlrpc 2021-02-24 11:21:19 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 (Errata Advisory for Openshift Logging 5.0.0), 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-2021:0652
Note You need to log in before you can comment on or make changes to this bug.