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

Bug 1509025

Summary:	Courier Fetch Error: unhandled courier request error: Request Timeout after 30000ms
Product:	OpenShift Container Platform	Reporter:	Steven Walter <stwalter>
Component:	Logging	Assignee:	Jeff Cantrill <jcantril>
Status:	CLOSED DUPLICATE	QA Contact:	Anping Li <anli>
Severity:	low	Docs Contact:
Priority:	medium
Version:	3.5.1	CC:	aos-bugs, jcantril, pweil, rmeggins, sradco
Target Milestone:	---
Target Release:	3.9.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-13 18:33:29 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 Steven Walter 2017-11-02 17:28:22 UTC

Description of problem:
Logging into kibana presents error:
Courier Fetch Error: unhandled courier request error: Request Timeout after 30000ms

Version-Release number of selected component (if applicable):
oc v3.5.5.31
Elasticsearch 3.5.0-15
Kibana 4.6


How reproducible:
Unconfirmed

Steps to Reproduce:
1. Log into kibana

Actual results:


Expected results:
 See dashboard

Additional info:
 https://bugzilla.redhat.com/show_bug.cgi?id=1508796

Comment 1 Steven Walter 2017-11-02 17:29:33 UTC

Issue appears very similar to  https://bugzilla.redhat.com/show_bug.cgi?id=1508796  --  I opened this for OCP (non-openshift online). Also note the version difference.

We checked Elasticsearch logs and they are healthy. I am requesting a screenshot of the issue. I am also uploading Kibana logs.

Comment 3 Rich Megginson 2017-11-02 17:59:28 UTC

Can we get the kibana proxy logs?  There is nothing in the kibana logs to indicate any error at all.

Comment 4 Jeff Cantrill 2017-11-03 15:15:08 UTC

Looking at the logs there is a period where Kibana was unable to find elasticsearch.  Could this be a networking/routing blip.  Later in the logs I see successful responses so I imagine maybe a refresh could be in order.

Comment 7 Jeff Cantrill 2017-11-06 16:57:12 UTC

I presume this is possibly related to load.  I will lower the priority in the hopes we can investigate further.

Comment 9 Jeff Cantrill 2018-02-13 18:33:29 UTC

The timeout can be extended with:

https://github.com/openshift/origin-aggregated-logging/pull/905

and backported to 3.7 with:

https://github.com/openshift/origin-aggregated-logging/pull/913

Additionally bumped the default:

https://github.com/openshift/origin-aggregated-logging/pull/934

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