Image uploads to the filesystem driver are not fully atomic
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
glance_store |
In Progress
|
Wishlist
|
Srinivas Sakhamuri |
Bug Description
When uploading to the filesystem store, the image is uploaded, checksummed, and added to the database, with appropriate rollback operations in place in case of failures. This is all good, but there are various corner-cases where partially-uploaded files can be left lying around in the filesystem_
Mostly this kind of thing interferes with operational processes we have that are external to Glance and not Glance itself. e.g., we have a monitoring process to reconcile the list/checksums of glance images against what's on-disk, and this occasionally goes funny on us. Additionally, we have a side-band backup/replication process that ends up occasionally transferring partial files for no reason.
Using a temporary upload space and moving the file into place on the filesystem store would cause a lot of our co-processes to work more cleanly, as well as reducing the risk of the _delete_partial job deleting the wrong thing should it go sideways.
Changed in glance: | |
status: | New → In Progress |
affects: | glance → glance-store |
Changed in glance-store: | |
importance: | Undecided → Wishlist |
tags: | added: lite-spec |
Changed in glance-store: | |
assignee: | Nicolas Simonds (nicolas.simonds) → Srinivas Sakhamuri (srinivas-sakhamuri) |
Because the Launchpad sync job is apparently asleep:
https:/ /review. openstack. org/82899