Bug 1701459 - context deadline exceeded for kube-controller-manager and kube-scheduler endpoints
Summary: context deadline exceeded for kube-controller-manager and kube-scheduler endp...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.1.0
Assignee: Frederic Branczyk
QA Contact: Junqi Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-19 06:06 UTC by Junqi Zhao
Modified: 2019-05-06 13:00 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-23 11:08:26 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
context deadline exceeded (153.87 KB, image/png)
2019-04-19 06:06 UTC, Junqi Zhao 		no flags Details
View All

Description Junqi Zhao 2019-04-19 06:06:22 UTC 
Created attachment 1556344 [details]
context deadline exceeded

Description of problem:
endpoints for kube-controller-manager and kube-scheduler are down, see the attached picture
error is "context deadline exceeded"

Version-Release number of selected component (if applicable):
4.0.0-0.nightly-2019-04-18-190537

How reproducible:
Always

Steps to Reproduce:
1. Check prometheus targets page
2.
3.

Actual results:
context deadline exceeded for kube-controller-manager and kube-scheduler endpoints

Expected results:
Should be UP

Additional info:
Comment 1 Frederic Branczyk 2019-04-23 09:35:07 UTC 
Could you re-test this with a more recent payload? The last PR to fix this was merged Thursday evening, I believe the payload you referenced just missed the last required change. The error message you quoted sounds exactly like that's what's happening.
Comment 2 Frederic Branczyk 2019-04-23 09:35:52 UTC 
As a side note, we tested on a latest payload and everything seems to work fine.
Comment 4 Junqi Zhao 2019-04-23 11:08:26 UTC 
no such issue with 4.0.0-0.nightly-2019-04-20-175518, close it as WORKSFORME
Note You need to log in before you can comment on or make changes to this bug.