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

Bug 2009756

Summary:	Kibana Yellow and Inaccessible - plugin:opendistro_security@6.8.1 Setting up index template. RHOCP 4.7
Product:	OpenShift Container Platform	Reporter:	Mani <mmohan>
Component:	Logging	Assignee:	Jeff Cantrill <jcantril>
Status:	CLOSED DUPLICATE	QA Contact:	Anping Li <anli>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.7	CC:	aos-bugs, periklis
Target Milestone:	---
Target Release:	---
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:	2021-10-21 12:00:11 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:

Description Mani 2021-10-01 13:51:46 UTC

Description of problem:
This bug is similar to https://bugzilla.redhat.com/show_bug.cgi?id=1913952.

Facing the same issue in 4.7.31, Durning cluster upgrades from 4.7.30 to 4.7.31 

Kibana is still in a Yellow state.

plugin:opendistro_security.1
Setting up index template

This could be solved by following https://access.redhat.com/solutions/5787261
Version-Release number of selected component (if applicable):


How reproducible:
Happened once

Steps to Reproduce:
1.N/A
2.
3.

Actual results:
Kibana is inaccessible for all users of the cluster.


Expected results:


Additional info:

Comment 3 Periklis Tsirakidis 2021-10-21 12:00:11 UTC

Please apply the workaround as mentioned in the verified solution: https://access.redhat.com/solutions/5787261

For the future, please open issues for the OpenShift Logging 5.x release directly on JIRA: https://issues.redhat.com/projects/LOG/issues
- If the indication for the issue is related to ES or Kibana please use Component: Log Exploration
- If the indication for the issue is related to Fluentd please use Component: Core

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