Bug 1870371 - Kibana status turns Yellow although elasticsearch is healthy
Summary: Kibana status turns Yellow although elasticsearch is healthy
Keywords:
Status: CLOSED DUPLICATE of bug 1885723
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 4.5
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 4.7.0
Assignee: Jeff Cantrill
QA Contact: Anping Li
URL:
Whiteboard: logging-exploration
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-19 21:33 UTC by Devendra Kulkarni
Modified: 2024-03-25 16:20 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-12 14:24:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Devendra Kulkarni 2020-08-19 21:33:38 UTC
Created attachment 1711944 [details]
Screenshot_kibana_status

Description of problem:

The logging stack works fine for several days and out of nowhere the Kibana state is Yellow. upon checking cluster health and status elasticsearch is healthy and green.


Version-Release number of selected component (if applicable): Elasticsearch/Kibana v6.8.1 
Red Hat OpenShift Container Platform v4.5


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Workaround to resolve the issue is to delete all the ".kibana*" indices.

Comment 2 ewolinet 2020-08-19 22:05:57 UTC
Seems to be related to this: https://github.com/opendistro-for-elasticsearch/security-kibana-plugin/issues/17#issuecomment-499229853

Workaround is to delete the kibana index that is being migrated.

Comment 3 Jeff Cantrill 2020-09-11 19:38:24 UTC
Moving to UpcomingSprint since they will not be addressed before EOD

Comment 4 Jeff Cantrill 2020-10-01 12:42:17 UTC
Moving to 4.7 to satisfy CF requirements for 4.6

Comment 5 Jeff Cantrill 2020-10-02 15:24:08 UTC
Marking UpcomingSprint as will not be merged or addressed by EOD

Comment 6 Jeff Cantrill 2020-10-12 14:24:20 UTC
Closing as a duplicate to https://bugzilla.redhat.com/show_bug.cgi?id=1885723  which better describes the issue.  Please re-associate the customer case.

*** This bug has been marked as a duplicate of bug 1885723 ***


Note You need to log in before you can comment on or make changes to this bug.