Glance's quota don't clean image_data if limit is reached

Bug #1262233 reported by Flavio Percoco on 2013-12-18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inessa Vasilevskaya

Bug Description

When the quota limit is reached, the image location is not cleaned up[0]. Notice that at this point *just* the locaiton should be deleted since the image data upload didn't succeed and the store should have already cleaned up the partially uploaded data.

Haojie Jia (jiahaojie) on 2013-12-23
Changed in glance:
assignee: nobody → Haojie Jia (jiahaojie)
Feilong Wang (flwang) on 2014-01-16
Changed in glance:
status: New → Triaged
importance: Undecided → Medium
Flavio Percoco (flaper87) wrote :

@Haojie Are you actually working on this?

Changed in glance:
assignee: Haojie Jia (jiahaojie) → nobody
Changed in glance:
assignee: nobody → Inessa Vasilevskaya (ivasilevskaya)

Hi, Flavio! Could you give more information on how to reproduce the bug?

My first thought was that on some quota violation (image size\locations) the bad location remains in image.locations list, but I've tried to reproduce this behaviour in api tests and everything works as expected.

Changed in glance:
status: Triaged → Incomplete
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers