yahoo-eng-team team mailing list archive

[wangxiyuan <wangxiyuan@xxxxxxxxxx>]

Public bug reported:

Reproduce:

1.create an image A, add backend 'X'  to it's location .

2.create another image B, add the same backend 'X' to it's location.

3.show the two image, their status are both 'active'.

4.delete image A.  After this setep, the backend X will be deleted as
well.

5. show the image B. Its status is still 'active'. Obviously, image B's
backend file  'X' has been deleted, So B can't be use anymore.


So IMHO, before we delete the backend file, we should check that whether the file is being use. If yes, we should not delete it directly.

** Affects: glance
     Importance: Undecided
     Assignee: wangxiyuan (wangxiyuan)
         Status: New

** Changed in: glance
     Assignee: (unassigned) => wangxiyuan (wangxiyuan)

** Summary changed:

- image's location was deleted while it was still being use.
+ image's backend file was deleted while it was still being use.

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

Title:
  image's backend file was deleted while it was still being use.

Status in Glance:
  New

Bug description:
  Reproduce:

  1.create an image A, add backend 'X'  to it's location .

  2.create another image B, add the same backend 'X' to it's location.

  3.show the two image, their status are both 'active'.

  4.delete image A.  After this setep, the backend X will be deleted as
  well.

  5. show the image B. Its status is still 'active'. Obviously, image
  B's backend file  'X' has been deleted, So B can't be use anymore.

  
  So IMHO, before we delete the backend file, we should check that whether the file is being use. If yes, we should not delete it directly.

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