Use of GreenAsyncPile can lose txn_id logging
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Object Storage (swift) |
In Progress
|
Medium
|
janonymous |
Bug Description
...if you don't do what swift.proxy.
AFAICT, this bug only affects the one other usage of GreenAsyncPile in Swift: swift.proxy.
Jan 9 09:01:27 container-server: "PUT /d22/162825/..." 201 - "PUT http://
Jan 9 09:01:27 container-server: "PUT /d13/162825/..." 201 - "PUT http://
Jan 9 09:01:27 object-server: "PUT /d23/98559/..." 201 - "PUT http://
Jan 9 09:01:27 swift: - - 09/Jan/
Jan 9 09:01:28 container-server: "PUT /d18/162825/..." 201 - "PUT http://
Jan 9 09:01:28 object-server: "PUT /d15/98559/..." 201 - "PUT http://
Jan 9 09:02:27 swift: ERROR with Object server 192.168.
CVE References
Changed in swift: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in swift: | |
assignee: | nobody → janonymous (janonymous) |
I wonder if we could make a factory for GreenAsyncPile's on a base wsgi application class such that when you get a pile it has the property of always passing in it's app's logger's thread locals into a wapped version of your spawned callable that fixes the locals inside of the spawn before calling your function...
Or maybe a TransactionIDPr eservingGreenAs yncPile class that takes a logger... that's probably simpler - we might even be able to audit for usage of GreenAsyncPile...