Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1479928

Summary:	Kibana nodejs runtime is not the same as the version distributed by Elastic
Product:	OpenShift Container Platform	Reporter:	Jeff Cantrill <jcantril>
Component:	Logging	Assignee:	Jeff Cantrill <jcantril>
Status:	CLOSED ERRATA	QA Contact:	Xia Zhao <xiazhao>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.6.0	CC:	aos-bugs, rmeggins, vcorrea, wsun
Target Milestone:	---
Target Release:	3.6.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1479934 (view as bug list)		Environment:
Last Closed:	2017-09-08 03:15:23 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:
Bug Blocks:	1479934, 1482226

Description Jeff Cantrill 2017-08-09 18:51:42 UTC

Description of problem:

Since the release of the v3.4 of the logging stack, Kibana has been running with v4.x of the nodejs runtime.  This version is different from that which is distributed with the Kibana download.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. os rsh $KIBANA_POD
2. ps -ef | grep node
3. with the binary found in 2: node --version

Actual results:
v4.7.3

Expected results:
v6.X

Additional info:
This maybe contributing to the OOM issues we have with Kibana. Regardless, we should 
be using the same version as the officially released product

Comment 3 Xia Zhao 2017-08-30 03:12:52 UTC

It's fixed, tested with kibana v3.6.173.0.23-2, the nodejs runtime is now v6.x:

# oc rsh logging-kibana-1-m24q3
Defaulting container name to kibana.

sh-4.2$ ps -ef | grep node
1000060+     13      1  0 Aug29 ?        00:00:00 /bin/bash /usr/bin/nodescl-node /usr/share/kibana/src/cli
1000060+     14     13  0 Aug29 ?        00:00:00 scl enable rh-nodejs6 -- node /usr/share/kibana/src/cli
1000060+     18     15  0 Aug29 ?        00:02:44 node /usr/share/kibana/src/cli
1000060+  39547  39506  0 03:06 ?        00:00:00 grep node

sh-4.2$ env | grep VER
KIBANA_VER=4.6.4
NODEJS_VERSION=6

sh-4.2$ /usr/bin/nodescl-node --version
v6.9.1

Test env:
# openshift version
openshift v3.6.173.0.21
kubernetes v1.6.1+5115d708d7
etcd 3.2.1

logging-kibana        v3.6.173.0.23-2     81a67557e904        7 hours ago         613.8 MB

Comment 7 errata-xmlrpc 2017-09-08 03:15: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:2642

Comment 8 Vítor Corrêa 2017-12-06 13:02:17 UTC

Hello, ihac with a very similar issue. BUT, the timeframe for missing 
.index is of two weeks. Can you confirm if is the same issue ? three of us confirmed:

ISSUE: After upgrade to ocp 3.6, es & kibana show logs fine, but it seems that the records from 2 weeks ago are inacessable.  
-We have kibana && kibana-ops. In kibana, we had an index ".all", and that index is gone. We created index "*", and can access that index.