Since currently we save image location to db only when image chunks got saved, so, even user executes 'image-delete' when glance-api comes back, from glance's eyes there's no any locations belong with that 'bad' image. so, the chunks couldn't be removed any more.
Since currently we save image location to db only when image chunks got saved, so, even user executes 'image-delete' when glance-api comes back, from glance's eyes there's no any locations belong with that 'bad' image. so, the chunks couldn't be removed any more.