yahoo-eng-team team mailing list archive

[Abhishek Kekane <abhishek.kekane@xxxxxxxxxxx>]

Public bug reported:

If the deletion of physical image failed with OSError for some reason,
it is not possible to delete the image using image-delete api call.

Please refer steps-to-reproduce.txt to reproduce the issue.

Possible solution:

Image status should not get updated in database to "deleted" if response
is HTTPForbidden (HTTP 403) or other than HTTP 200

** Affects: glance
     Importance: Undecided
     Assignee: Abhishek Kekane (abhishek-kekane)
         Status: New


** Tags: ntt

** Attachment added: "steps-to-reproduce.txt"
   https://bugs.launchpad.net/bugs/1276142/+attachment/3968664/+files/steps-to-reproduce.txt

** Changed in: glance
     Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1276142

Title:
  Physical image can not be deleted again if deletion is failed with
  OSError for some reason

Status in OpenStack Image Registry and Delivery Service (Glance):
  New

Bug description:
  If the deletion of physical image failed with OSError for some reason,
  it is not possible to delete the image using image-delete api call.

  Please refer steps-to-reproduce.txt to reproduce the issue.

  Possible solution:

  Image status should not get updated in database to "deleted" if
  response is HTTPForbidden (HTTP 403) or other than HTTP 200

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1276142/+subscriptions