Bug 1749618 - Kibana pod failed to start: /opt/rh/rh-nodejs6/root/usr/bin/node: bad option: --max-http-header-size=65536
Summary: Kibana pod failed to start: /opt/rh/rh-nodejs6/root/usr/bin/node: bad option:...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.2.0
Assignee: Jeff Cantrill
QA Contact: Qiaoling Tang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-06 02:27 UTC by Qiaoling Tang
Modified: 2019-10-16 06:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-16 06:40:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:40:43 UTC

Description Qiaoling Tang 2019-09-06 02:27:47 UTC 
Description of problem:
The kibana pod couldn't start:

$ oc logs -c kibana kibana-66599964b7-pw9hb
#The following values dynamically added from environment variable overrides:
Using NODE_OPTIONS: '--max_old_space_size=368' Memory setting is in MB
/opt/rh/rh-nodejs6/root/usr/bin/node: bad option: --max-http-header-size=65536


Version-Release number of selected component (if applicable):
ose-logging-kibana5/images/v4.2.0-201909051819

How reproducible:
Always

Steps to Reproduce:
1.deploy logging
2.check pod status
3.

Actual results:


Expected results:


Additional info:
Comment 1 Anping Li 2019-09-10 08:21:55 UTC 
The bug is blocking the kibana cases testing and some bugs verification.
Comment 4 Qiaoling Tang 2019-09-11 06:42:44 UTC 
Waiting for new image.
Comment 5 Qiaoling Tang 2019-09-12 05:54:46 UTC 
Verified with ose-logging-kibana5-v4.2.0-201909112219
Comment 6 errata-xmlrpc 2019-10-16 06:40:35 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-2019:2922
Note You need to log in before you can comment on or make changes to this bug.