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

Bug 1726434

Summary: kibana presenting blank page or timeout
Product: OpenShift Container Platform Reporter: Jeff Cantrill <jcantril>
Component: LoggingAssignee: Jeff Cantrill <jcantril>
Status: CLOSED ERRATA QA Contact: Anping Li <anli>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 4.1.0CC: anli, aos-bugs, eparis, jcantril, jfoots, mirollin, rmeggins, rsandu, stwalter, vlaad
Target Milestone: ---Keywords: Reopened
Target Release: 4.1.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: The dynamic seeding is inefficient and user's with visibility to a large number of projects exposes this issue by making too many calls to the Elasticsearch cluster. Additionally, there is no caching for user requests causing the seeding process to occur more frequently. Consequence: Calls to Elasticsearch can timeout before a response is returned. Fix: Introduce caching of the API calls and ACL seeding Result: Dynamic seeding is more efficient reducing the opportunity for page timeouts.
Story Points: ---
Clone Of: 1705589 Environment:
Last Closed: 2019-08-28 19:54:45 UTC Type: ---
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: 1705589    
Bug Blocks: 1726433    

Comment 2 Anping Li 2019-08-02 09:21:15 UTC
Regression pass on openshift/ose-logging-kibana5:v4.1.9-201907311355

Comment 7 Anping Li 2019-08-16 05:52:23 UTC
Test blocked by https://bugzilla.redhat.com/show_bug.cgi?id=1741753

Comment 8 Anping Li 2019-08-19 06:19:12 UTC
Verified in 4.1.12

Comment 12 Anping Li 2019-08-26 03:44:53 UTC
Regression pass in 4.1.13

Comment 14 errata-xmlrpc 2019-08-28 19:54:45 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-2019:2547