v1 API is deprecated.
** Changed in: glance
Status: In Progress => Invalid
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
Images in inconsistent state when calls to registry fail during image
Status in Glance:
Status in Glance juno series:
Status in Glance kilo series:
Status in Glance liberty series:
Status in OpenStack Security Advisory:
 shows a sample image that was left in an inconsistent state when a
call to registry failed during image deletion.
Glance v1 API makes two registry calls when deleting an image.
The first call  is made to to set the status of an image to
And, the other , to delete the rest of the metadata, which sets
'deleted_at' and 'deleted' fields in the db.
If the first call fails, the image deletion request fails and the image is
left intact in it's previous status.
However, if the first call succeeds and the second one fails, the image is
left in an inconsistent status where it's status is set to
pending_delete/deleted but it's 'deleted_at' and 'deleted' fields are not set.
If delayed delete is turned on, these images are never collected by the
scrubber as they won't appear as deleted images because their deleted field is
not set. So, these images will continue to occupy storage in the backend.
Also, further attempts at deleting these images will fail with a 404 because
the status is already set to pending_delete/deleted.
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : email@example.com
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp