filesystem store does not clean up after premature termination of image upload
Bug #1104924 reported by
Eoghan Glynn
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Glance |
Fix Released
|
Medium
|
Eoghan Glynn | ||
Folsom |
Fix Released
|
Medium
|
Eoghan Glynn | ||
Grizzly |
Fix Released
|
Medium
|
Eoghan Glynn |
Bug Description
If a PUT or POST of image content is terminated prematurely by the client, the image is marked as killed.
In the case of swift and s3, such partial uploads are properly cleaned up and do not leave behind dangling image fragments visible in store.
However this is not the case for the filesystem store, where the partially saved image file is left behind in the data directory.
Changed in ceilometer: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
milestone: | none → grizzly-3 |
assignee: | nobody → Eoghan Glynn (eglynn) |
status: | Confirmed → In Progress |
affects: | ceilometer → glance |
Changed in glance: | |
milestone: | grizzly-3 → none |
milestone: | none → grizzly-3 |
tags: | added: folsom-backport-potential |
tags: | removed: folsom-backport-potential |
Changed in glance: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/20472
Review: https:/