yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #02586
[Bug 1163020] Re: Unclear behavior in V1 API when deleting a pending_delete image
** Changed in: glance
Status: Fix Committed => Fix Released
** Changed in: glance
Milestone: None => havana-1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1163020
Title:
Unclear behavior in V1 API when deleting a pending_delete image
Status in OpenStack Image Registry and Delivery Service (Glance):
Fix Released
Bug description:
Glance version: Grizzly-rc1
'delay_delete' is ON in the following tests.
v1 api behavior
1st deletion:
- image status changes to 'pending_delete'
- Delete metadata (marked as deleted)
- return 200 - OK
2nd deletion:
- image status changes to 'deleted'.
- But still leave the image data for scrubber to delete.
- return 200- OK
3rd deletion:
- image status is still 'deleted'
- still leave the image data for scrubber to delete.
- return 403 - Forbidden
v2 api behavior
1st deletion:
- status changes to pending_delete
- return 204 No Content
2nd deletion
- status is still pending_delete
- return 404 Not Found
3rd deletion
- status is still pending_delete
- return 404 Not Found
So V2 behavior looks more clear and consistent, however v1 behavior
looks vague.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1163020/+subscriptions