Bug 1437366 - Kibana UI Shard failure
Summary: Kibana UI Shard failure
Keywords:
Status: CLOSED DUPLICATE of bug 1444106
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 3.4.1
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: ---
Assignee: Jeff Cantrill
QA Contact: Xia Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-30 08:08 UTC by Mangirdas Judeikis
Modified: 2020-09-10 10:24 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-26 23:00:03 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
error (104.33 KB, image/png)
2017-03-30 08:08 UTC, Mangirdas Judeikis 		no flags Details
View All

Description Mangirdas Judeikis 2017-03-30 08:08:38 UTC 
Created attachment 1267440 [details]
error

Description of problem:
If you deploy EFK stack from version 3.4.1 you get errors in Kibana UI stating there is an issue with shards. Pic attached. 

If you press from Discover to Dashboard or any other tab you will get all good. So suspect this is UI bug in Kibana. 


Version-Release number of selected component (if applicable):
registry.access.redhat.com/openshift3/logging-kibana:3.4.1


How reproducible:
Run EFK stack from image 3.4.1
Access UI of Kibana 
Enjoy.
Comment 1 Peter Portante 2017-03-30 10:20:38 UTC 
Seems like this is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1426061.
Comment 2 Mangirdas Judeikis 2017-03-30 10:40:40 UTC 
Yes. 

We need to wait until fix (3.5.0 images) will land to access registry and we will be able to validate
Comment 3 Jeff Cantrill 2017-03-30 12:42:46 UTC 
I also wonder if this is related to issues we have seen when there is no data available. Setting the severity to low since its non-blocking
Comment 4 Joe Stewart 2017-04-25 13:38:22 UTC 
We're experiencing this issue as well. Any update?
Comment 5 Rich Megginson 2017-04-26 23:00:03 UTC 
I think this is a dup of https://bugzilla.redhat.com/show_bug.cgi?id=1444106

*** This bug has been marked as a duplicate of bug 1444106 ***
Note You need to log in before you can comment on or make changes to this bug.