Bug 1475529

Summary: Backtrace in api server log
Product: OpenShift Container Platform Reporter: Eric Paris <eparis>
Component: MasterAssignee: David Eads <deads>
Status: CLOSED WORKSFORME QA Contact: DeShuai Ma <dma>
Severity: low Docs Contact:
Priority: low    
Version: 3.6.0CC: aos-bugs, decarr, jokerman, mfojtik, mmccomas, sjenning
Target Milestone: ---   
Target Release: 3.8.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: 2017-09-13 17:41:28 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:
Attachments:
Description Flags
"backtrace" none

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.