© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I'm using Icehouse (Ubuntu 14.04) and a plain directory as a backend and I can confirm that in emergency cases when something get stuck e.g. in SAVING state, DELETE just removes data from the database, but the image itself remains on the disk.
In my case during image-create there was an error related to authentication. It looks like the token has expired - the image had 20GB, plus slow connection, so it all was slow.
In general when downloading is finished, there is a request to update the state and because of expired token, NotAuthenticated error is thrown. Later glance tries to KILL the image, but also NotAuthenticated error occurs and Image is stuck in SAVING state. So I just deleted broken image, but after few days when I checked the directory with images I've noticed that too many images are there and I've figured out that all images deleted during that weird error were just deleted from glance's database, so they are no longer on images' list, but they remain on the disk.