← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 2097414] [NEW] The glance scrubber cannot delete locations in database of url images when use delayed delete

 

Public bug reported:

1.Set delayed_delete is true in glance-api.conf

2.Create an image by URL, then delete the image.
Because of delayed_delete is true, the image is in pending delete state in the database.

3.Using the glance scrubber to clear image records, the script log reports error such as:
2025-01-23 20:17:48.191 484 INFO glance.scrubber [-] Scrubbing image 76ab1055-xxxx-xxxx-xxxx-xxxxxxxxxxxx from 1 locations.
2025-01-23 20:17:48.192 484 ERROR glance.scrubber [-] Unable to scrub image 76ab1055-xxxx-xxxx-xxxx-xxxxxxxxxxxx from a location. Reason: Deleting images from this store is not supported. : glance_store.exceptions.StoreDeleteNotSupported: Deleting images from this store is not supported.
2025-01-23 20:17:48.193 484 WARNING glance.scrubber [-] One or more image locations couldn't be scrubbed from backend. Leaving image '76ab1055-xxxx-xxxx-xxxx-xxxxxxxxxxxx' in 'pending_delete' status

I noticed that in glance_store/capabilities.py, op_cap_map states that delete requires WRITE_ACCESS permission.
And in glance_store/_drivers/http.py, the _CAPABILITIES is (capabilities.BitMasks.READ_ACCESS | capabilities.BitMasks.DRIVER_REUSABLE)

Unfortunately, I haven't found any documentation on why HTTP deletion
operations are not allowed yet.

** 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/2097414

Title:
  The glance scrubber cannot delete locations in database of url images
  when use delayed delete

Status in Glance:
  New

Bug description:
  1.Set delayed_delete is true in glance-api.conf

  2.Create an image by URL, then delete the image.
  Because of delayed_delete is true, the image is in pending delete state in the database.

  3.Using the glance scrubber to clear image records, the script log reports error such as:
  2025-01-23 20:17:48.191 484 INFO glance.scrubber [-] Scrubbing image 76ab1055-xxxx-xxxx-xxxx-xxxxxxxxxxxx from 1 locations.
  2025-01-23 20:17:48.192 484 ERROR glance.scrubber [-] Unable to scrub image 76ab1055-xxxx-xxxx-xxxx-xxxxxxxxxxxx from a location. Reason: Deleting images from this store is not supported. : glance_store.exceptions.StoreDeleteNotSupported: Deleting images from this store is not supported.
  2025-01-23 20:17:48.193 484 WARNING glance.scrubber [-] One or more image locations couldn't be scrubbed from backend. Leaving image '76ab1055-xxxx-xxxx-xxxx-xxxxxxxxxxxx' in 'pending_delete' status

  I noticed that in glance_store/capabilities.py, op_cap_map states that delete requires WRITE_ACCESS permission.
  And in glance_store/_drivers/http.py, the _CAPABILITIES is (capabilities.BitMasks.READ_ACCESS | capabilities.BitMasks.DRIVER_REUSABLE)

  Unfortunately, I haven't found any documentation on why HTTP deletion
  operations are not allowed yet.

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