yahoo-eng-team team mailing list archive

["Jesse J. Cook" <jesse.cook@xxxxxxxxxxxxx>]

Public bug reported:

The scrubber can leave orphaned objects and db records in error / edge
cases. This is because the order in which it updates the DB and object
store. Recommended solution:

For each image that has status pending_delete:
    For each image location that has status pending_delete:
        Delete the object in the object store
        If error other than object not found, continue
        Mark image location status as deleted
    If all image locations are deleted, mark image as deleted
    Else if no image locations are marked as pending_delete, change status to something else??? # I suppose it's possible an image_location would still be active or some other non-deleted status. I don't think we want to orphan the image_location by marking the image deleted in this case.

** Affects: glance
     Importance: Undecided
         Status: New

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

Title:
  scrubber edge cases orphan objects and records

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

Bug description:
  The scrubber can leave orphaned objects and db records in error / edge
  cases. This is because the order in which it updates the DB and object
  store. Recommended solution:

  For each image that has status pending_delete:
      For each image location that has status pending_delete:
          Delete the object in the object store
          If error other than object not found, continue
          Mark image location status as deleted
      If all image locations are deleted, mark image as deleted
      Else if no image locations are marked as pending_delete, change status to something else??? # I suppose it's possible an image_location would still be active or some other non-deleted status. I don't think we want to orphan the image_location by marking the image deleted in this case.

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