Bug 1731827

Summary: [4.1.7] [Regression]"server returned HTTP status 500 Internal Server Error" for some kubelet endpoints
Product: OpenShift Container Platform Reporter: Junqi Zhao <juzhao>
Component: NodeAssignee: Ryan Phillips <rphillips>
Status: CLOSED ERRATA QA Contact: Junqi Zhao <juzhao>
Severity: high Docs Contact:
Priority: high    
Version: 4.1.zCC: aos-bugs, chuyu, cmarches, jokerman, mmccomas, rphillips, sjenning
Target Milestone: ---Keywords: Regression
Target Release: 4.1.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1750963 (view as bug list) Environment:
Last Closed: 2019-08-15 14:24:02 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:    
Bug Blocks: 1750963    
Attachments:
Description Flags
kubelet logs
none
Prometheus 500 issue configuration 4.1.4 none

Comment 3 Junqi Zhao 2019-07-23 01:34:02 UTC
Created attachment 1592721 [details]
kubelet logs

Comment 6 Ryan Phillips 2019-07-30 16:01:23 UTC
Origin PR: https://github.com/openshift/origin/pull/23513

Comment 7 Seth Jennings 2019-07-31 14:19:33 UTC
*** Bug 1734635 has been marked as a duplicate of this bug. ***

Comment 8 Ryan Phillips 2019-07-31 17:46:58 UTC
Origin master PR merged.

Origin 4.1 Pick PR: https://github.com/openshift/origin/pull/23524

Comment 9 Seth Jennings 2019-08-05 14:21:47 UTC
Waiting on cherry-pick-approved for the backport PR

Comment 17 Caden Marchese 2019-08-09 17:19:07 UTC
Created attachment 1602254 [details]
Prometheus 500 issue configuration 4.1.4

Customer is experiencing the 500 error with Prometheus on 4.1.4. Attaching configuration information / reproducer from bug 1712645 in case it will help.

Comment 20 errata-xmlrpc 2019-08-15 14:24:02 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:2417