Glance caching not correctly handling backend failures
Bug #1045792 reported by
Paul Bourke
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Glance |
Fix Released
|
Medium
|
Paul Bourke |
Bug Description
Currently the cache assumes any exception fired is the result of a problem writing to the cache, and tries to continue the response. In the event of a backend failure this causes clients to become stuck waiting for data that isn't coming.
Also, if the cache file is bad, either through the backend serving out corrupt data or otherwise, the file is still placed in and subsequently served out of the cache.
Changed in glance: | |
milestone: | none → folsom-rc1 |
status: | Fix Committed → Fix Released |
Changed in glance: | |
importance: | Undecided → Medium |
Changed in glance: | |
milestone: | folsom-rc1 → 2012.2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/12347
Review: https:/