OpenStack Object Storage (swift)

catch_errors middleware needs more verbose logging

Bug #703095 reported by Chuck Thier
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Object Storage (swift)
Invalid
Medium
Chuck Thier
OpenStack Object Storage (swift) 1.2.0 "swift-1.2.0"

Bug Description

Currently, the catch_errors middleware will catch the error, but just prints the error message. This doesn't give enough context as to where the error happened, so it should include the traceback as well.

Chuck Thier (cthier)
Changed in swift:
status: New → Triaged
importance: Undecided → Medium
assignee: nobody → Chuck Thier (cthier)
milestone: none → 1.2.0
Revision history for this message
clayg (clay-gerrard) wrote :

???

wfm

Jan 14 16:58:20 rackswift proxy-server Error: global name 'asdf' is not defined: #012Traceback (most recent call last):#012 File "/home/clayg/local/swift/common/middleware/catch_errors.py", line 37, in __call__#012 return self.app(env, start_response)#012 File "/home/clayg/local/swift/common/middleware/healthcheck.py", line 34, in __call__#012 asdf#012NameError: global name 'asdf' is not defined

Changed in swift:
status: Triaged → Incomplete
Revision history for this message
Chuck Thier (cthier) wrote :

hrm... I could have sworn that it didn't do that a while ago when I tested it :/

Oh well... glad it works as expected :)

Changed in swift:
status: Incomplete → Won't Fix
Chuck Thier (cthier)
Changed in swift:
status: Won't Fix → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.