Bug 1473599 - 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.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 3.5.z
Assignee: Jeff Cantrill
QA Contact: Xia Zhao
URL:
Whiteboard:
Depends On:
Blocks: 1474489
TreeView+ depends on / blocked
 
Reported: 2017-07-21 09:24 UTC by Vladislav Walek
Modified: 2020-09-10 10:59 UTC (History)
7 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:
: 1474489 (view as bug list)
Environment:
Last Closed: 2017-08-31 17:00:23 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:1828 0 normal SHIPPED_LIVE OpenShift Container Platform 3.5, 3.4, and 3.3 bug fix update 2017-08-31 20:59:56 UTC

Description Vladislav Walek 2017-07-21 09:24:47 UTC 
Description of problem:

When deploying new image of Kibana, the Kibana fails on error:

/run.sh: line 44: KIBANA_MEMORY_LIMIT: unbound variable

Version-Release number of selected component (if applicable):
OpenShift Container Platfrom 3.5
registry.access.redhat.com/openshift3/logging-kibana:3.5.0-17

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 7 Jeff Cantrill 2017-07-24 18:07:15 UTC 
Upstream fix: openshift/origin-aggregated-logging/pull/541
Comment 10 Xia Zhao 2017-08-03 09:34:05 UTC 
It's fixed, tested with v3.5 images, kibana is back with log entries presented on UI. Set to verified. 

Test env:
# openshift version
openshift v3.5.5.31.6
kubernetes v1.5.2+43a9be4
etcd 3.1.0
 
Images tested with:
logging-kibana          v3.5                77136c6a8121        7 days ago          342.6 MB
Comment 12 errata-xmlrpc 2017-08-31 17:00:23 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/RHBA-2017:1828
Note You need to log in before you can comment on or make changes to this bug.