trans-id not always set correctly
Bug #872013 reported by
David Goetz
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Object Storage (swift) |
Fix Released
|
Medium
|
David Goetz | ||
Bug Description
The trans ID that gets set in catch-errors only set the env not what the LogAdapter (threading.local) uses in exceptions:
The setting of the trans id should be consolided into catcherrors and then we need to make sure that it doens't get overriden somewhere else. Right now, if the trans-id in the logger doesn't get manually set like it does in the proxy server (because the request doesn't get to the proxy server because it gets ratelimited), then two requests can log the same transaction id.
problem with above solution is: what if the catch errors middleware is not being used?
| Changed in swift: | |
| milestone: | none → 1.4.4 |
| importance: | Undecided → Medium |
| assignee: | nobody → David Goetz (david-goetz) |
| status: | New → In Progress |
| Changed in swift: | |
| status: | In Progress → Fix Committed |
| Changed in swift: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
