Bug 1474489 - KIBANA_MEMORY_LIMIT: unbound variable
Summary: KIBANA_MEMORY_LIMIT: unbound variable
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Jeff Cantrill
QA Contact: Xia Zhao
URL:
Whiteboard:
Depends On: 1473599
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-24 18:07 UTC by Jeff Cantrill
Modified: 2020-09-10 11:01 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: The run.sh script was expecting the var to be defined by the DC but when the pod was restarted it pulled a new image and didn't have the defined var in the DC Consequence: Fix: Default a value for KIBANA_MEMORY_LIMIT Result:
Clone Of: 1473599
Environment:
Last Closed: 2017-08-10 05:32:16 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift origin-aggregated-logging pull 542 0 None None None 2017-07-24 18:13:18 UTC
Red Hat Product Errata RHEA-2017:1716 0 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.6 RPM Release Advisory 2017-08-10 09:02:50 UTC

Comment 1 Jeff Cantrill 2017-07-24 18:13:19 UTC 
Upstream fix: https://github.com/openshift/origin-aggregated-logging/pull/542
Comment 2 openshift-github-bot 2017-07-24 23:01:02 UTC 
Commit pushed to master at https://github.com/openshift/origin-aggregated-logging

https://github.com/openshift/origin-aggregated-logging/commit/5bc62fc4796d9e057ed2df3b8f85c646ca34238e
bug 1474489. Default KIBANA_MEMORY_LIMIT

(cherry picked from commit 5ec45f1cc9934d652092bc425b7d284bb9328835)
Comment 5 Xia Zhao 2017-07-31 09:37:19 UTC 
It's fixed, tested with kibana v3.6.172.0.4-1 on OCP 3.6, it is back and logging UI worked fine:

Image tested with:
logging-kibana             v3.6                515b4f7211f9        3 hours ago         342.4 MB
logging-kibana             v3.6.172.0.4-1      515b4f7211f9        3 hours ago         342.4 MB
Comment 7 errata-xmlrpc 2017-08-10 05:32:16 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, 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/RHEA-2017:1716
Note You need to log in before you can comment on or make changes to this bug.