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

Bug 1598305

Summary:	[3.9]Cluster admin, click "View Archive" shows no result in Kibana due to default index pattern is ".operations.*"
Product:	OpenShift Container Platform	Reporter:	Junqi Zhao <juzhao>
Component:	Logging	Assignee:	Jeff Cantrill <jcantril>
Status:	CLOSED ERRATA	QA Contact:	Anping Li <anli>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.9.0	CC:	anli, aos-bugs, jcantril, jmalde, qitang, rkant, rmeggins, xtian
Target Milestone:	---
Target Release:	3.9.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: Kibana index pattern seeding was modified to reduce the number of entries in the droplist that were visible to cluster admins. Consequence: Cluster-admin's navigating to Kibana for logging from the web console were no longer sent to the correct URL. Fix: Take into consideration a user's cluster-admin role when creating the web console link to pod logs in Kibana Result: The link is created correctly.	Story Points:	---
Clone Of:	1587807	Environment:
Last Closed:	2018-12-13 19:26:59 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:
Bug Depends On:	1587807, 1624406
Bug Blocks:

Comment 1 Jeff Cantrill 2018-07-23 13:14:43 UTC

*** Bug 1603549 has been marked as a duplicate of this bug. ***

Comment 3 Jeff Cantrill 2018-09-04 15:33:18 UTC

Work around is to go straight to Kibana and choose the correct index pattern or link from the web console and choose the appropriate index pattern

Comment 4 Jeff Cantrill 2018-10-19 20:39:28 UTC

https://github.com/openshift/origin-web-console/pull/3088

Comment 8 Qiaoling Tang 2018-11-29 03:33:55 UTC

Verified in ose-web-console-v3.9.55-1.

Comment 10 errata-xmlrpc 2018-12-13 19:26:59 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:3748