Bug 1474489
| Summary: | KIBANA_MEMORY_LIMIT: unbound variable | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jeff Cantrill <jcantril> |
| Component: | Logging | Assignee: | Jeff Cantrill <jcantril> |
| Status: | CLOSED ERRATA | QA Contact: | Xia Zhao <xiazhao> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.6.0 | CC: | aos-bugs, jwozniak, pweil, rmeggins, rromerom, smunilla, vwalek, xiazhao |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| 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:
|
Story Points: | --- |
| Clone Of: | 1473599 | Environment: | |
| Last Closed: | 2017-08-10 05:32:16 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1473599 | ||
| Bug Blocks: | |||
|
Comment 1
Jeff Cantrill
2017-07-24 18:13:19 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) 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 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 |