Bug 1870371
| Summary: | Kibana status turns Yellow although elasticsearch is healthy | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Devendra Kulkarni <dkulkarn> |
| Component: | Logging | Assignee: | Jeff Cantrill <jcantril> |
| Status: | CLOSED DUPLICATE | QA Contact: | Anping Li <anli> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 4.5 | CC: | aconway, aos-bugs, ewolinet, mburke |
| Target Milestone: | --- | ||
| Target Release: | 4.7.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | logging-exploration | ||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-10-12 14:24:20 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: | |||
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. Moving to UpcomingSprint since they will not be addressed before EOD Moving to 4.7 to satisfy CF requirements for 4.6 Marking UpcomingSprint as will not be merged or addressed by EOD 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 *** |
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.