Bug 1475529 - Backtrace in api server log
Summary: Backtrace in api server log
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Master
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 3.8.0
Assignee: David Eads
QA Contact: DeShuai Ma
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-26 20:45 UTC by Eric Paris
Modified: 2017-09-13 17:41 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-13 17:41:28 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
"backtrace" (5.59 KB, text/plain)
2017-07-26 20:45 UTC, Eric Paris 		no flags Details
View All

Description Eric Paris 2017-07-26 20:45:16 UTC 
oc v3.6.170

Posting the log in an attachment to make it more readable.

I'd like to know what this means or what I should do since I see many things like this in my production cluster
Comment 1 Eric Paris 2017-07-26 20:45:42 UTC 
Created attachment 1305031 [details]
"backtrace"
Comment 2 David Eads 2017-07-27 18:59:57 UTC 
I need to figure out if we're returning the right error code.  I was going to suppress 504s, but it looks like we're returning 500s.  The stacks are easy to suppress on a per-code basis, but we don't want to suppress useful ones.
Note You need to log in before you can comment on or make changes to this bug.