Bug 1944048 - Logging 5.0 - Elasticsearch-operator can not start due to resource limitation
Summary: Logging 5.0 - Elasticsearch-operator can not start due to resource limitation
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 4.8
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: ewolinet
QA Contact: Giriyamma
URL:
Whiteboard:
Depends On: 1939979 1944049
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-29 06:44 UTC by Giriyamma
Modified: 2021-04-20 12:54 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
* Previously, an update in the cluster service version (CSV) accidentally introduced resources and limits for the OpenShift Elasticsearch operator container. Under specific conditions, this caused an out-of-memory condition that terminated the Elasticsearch operator pod. The current release fixes this issue by removing the CSV resources and limits for the operator container. Now, the operator gets scheduled without issues. (link:https://issues.redhat.com/browse/LOG-1254[*LOG-1254*])
Clone Of: 1939979
Environment:
Last Closed: 2021-04-06 02:59:08 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 1 Anping Li 2021-04-06 02:37:27 UTC 
Verified on elasticsearch-operator.5.0.2-9
Comment 2 Anping Li 2021-04-06 02:59:08 UTC 
Openshift-logging use jira rather than buzilar. So duplicated to https://issues.redhat.com/browse/LOG-1254 and close wontfix here.
Note You need to log in before you can comment on or make changes to this bug.