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

Bug 1595956

Summary: Kibana dashboards do not work with Kibana5/Elasticsearch5
Product: OpenShift Container Platform Reporter: Rich Megginson <rmeggins>
Component: LoggingAssignee: Rich Megginson <rmeggins>
Status: CLOSED ERRATA QA Contact: Anping Li <anli>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.11.0CC: aos-bugs, jcantril, rmeggins
Target Milestone: ---Keywords: TestBlocker
Target Release: 3.11.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openshift3/ose-logging-elasticsearch5:v3.11.0-0.17.0.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-11 07:20:43 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:
Attachments:
Description Flags
The kibaban pod logs none

Description Rich Megginson 2018-06-27 22:00:39 UTC
Description of problem:
es_load_kibana_ui_objects does not work with Kibana5/Elasticsearch5

Running with output to stdout:
{"took":0,"errors":true,"items":[{"create":{"_index":"","_type":"dashboard","_id":"Kubernetes-Overview","status":500,"error":{"type":"string_index_out_of_bounds_exception","reason":"String index out of range: 0"}}},{"create":{"_index":"","_type":"search","_id":"k8s-logs","status":500,"error":{"type":"string_index_out_of_bounds_exception","reason":"String index out of range: 0"}}},{"create":{"_index":"","_type":"visualization","_id":"Kubernetes-Logs-by-Namespace,-DC,-Pod,-Container","status":500,"error":{"type":"string_index_out_of_bounds_exception","reason":"String index out of range: 0"}}},{"create":{"_index":"","_type":"visualization","_id":"Kubernetes-Logs-over-Time-w-slash-Container-Name","status":500,"error":{"type":"string_index_out_of_bounds_exception","reason":"String index out of range: 0"}}}]}+ info Success

We need to have brand new json files for the ui objects for es5/kibana5


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 openshift-github-bot 2018-07-02 22:24:57 UTC
Commits pushed to master at https://github.com/openshift/origin-aggregated-logging

https://github.com/openshift/origin-aggregated-logging/commit/977b9c0267dae76000df2b27207972c0a7d32258
Bug 1595956 - Kibana dashboards do not work with Kibana5/Elasticsearch5

https://bugzilla.redhat.com/show_bug.cgi?id=1595956
es5 does not like leading //

https://github.com/openshift/origin-aggregated-logging/commit/1287aedf2ad05554d1cafa2bf38710dd0a738ce0
Merge pull request #1225 from richm/bug-1595956

Bug 1595956 - Kibana dashboards do not work with Kibana5/Elasticsearch5

Comment 2 Anping Li 2018-08-06 10:05:31 UTC
Created attachment 1473559 [details]
The kibaban pod logs

Login as a cluster-admin.  No default index pattern, and couldn't create index pattern. It report the following messages.  (Saml method are used for the attached logs, I had gotten same error when use Allowall method)

[object Object]: [security_exception] no permissions for [indices:data/read/field_caps] and User [name=CN=system.logging.kibana,OU=OpenShift,O=Logging, roles=[]]

Comment 3 Jeff Cantrill 2018-08-06 13:59:47 UTC
Rich,

I am seeing some general permission issues I'm trying to resolve now which I've tried to capture in [1].  I believe the fix to this may resolve the issue you are seeing here.

[1] https://github.com/fabric8io/openshift-elasticsearch-plugin/issues/155

Comment 4 Rich Megginson 2018-08-06 15:32:27 UTC
(In reply to Anping Li from comment #2)
> Created attachment 1473559 [details]
> The kibaban pod logs
> 
> Login as a cluster-admin.  No default index pattern, and couldn't create
> index pattern. It report the following messages.  (Saml method are used for
> the attached logs, I had gotten same error when use Allowall method)
> 
> [object Object]: [security_exception] no permissions for
> [indices:data/read/field_caps] and User
> [name=CN=system.logging.kibana,OU=OpenShift,O=Logging, roles=[]]

This is a different issue - "Can't Login to Kibana5"

Comment 5 Jeff Cantrill 2018-08-08 20:17:52 UTC
Testing with https://github.com/openshift/origin-aggregated-logging/pull/1273 I am able to run script:

# oc exec -c elasticsearch $pod -- es_load_kibana_ui_objects admin
[2018-08-08 10:04:18,222][INFO ][container.run            ] Adding Kibana dashboards and other UI objects for user admin index .kibana.d033e22ae348aeb5660fc2140aec35850c4da997
[2018-08-08 10:04:18,223][INFO ][container.run            ] Adding the index pattern for project.* . . .
[2018-08-08 10:04:18,487][INFO ][container.run            ] Adding the Kibana UI objects . . .
[2018-08-08 10:04:18,779][INFO ][container.run            ] Success

Comment 6 Rich Megginson 2018-08-08 20:26:53 UTC
(In reply to Jeff Cantrill from comment #5)
> Testing with
> https://github.com/openshift/origin-aggregated-logging/pull/1273 I am able
> to run script:
> 
> # oc exec -c elasticsearch $pod -- es_load_kibana_ui_objects admin
> [2018-08-08 10:04:18,222][INFO ][container.run            ] Adding Kibana
> dashboards and other UI objects for user admin index
> .kibana.d033e22ae348aeb5660fc2140aec35850c4da997
> [2018-08-08 10:04:18,223][INFO ][container.run            ] Adding the index
> pattern for project.* . . .
> [2018-08-08 10:04:18,487][INFO ][container.run            ] Adding the
> Kibana UI objects . . .
> [2018-08-08 10:04:18,779][INFO ][container.run            ] Success

And you are able to login to kibana?

Comment 7 Jeff Cantrill 2018-08-08 21:00:02 UTC
Yes

Comment 8 Anping Li 2018-08-21 02:47:51 UTC
The kibana can show index with v3.11.0-0.19.0.0

Comment 10 errata-xmlrpc 2018-10-11 07:20:43 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-2018:2652