Shouldn't Nova do cleanup the resources that are created implicitly?

asked 2015-03-05 06:32:45 -0600

nithya-ganesan gravatar image

I have a question regarding the implicit volume resources that created by Nova during persistent VM's snapshot creation. Here is a sample scenario that leaves a set of volume resources as residue,

  1. Create a bootable volume, bv_1
  2. Create an instance vm_1, from the bootable volume bv_1
  3. Create an image snapshot of vm_1, vm_1_img. This implicitly creates a volume snapshot of bv_1, bv_1_vsnap.
  4. Create an instance vm_2 from vm_1_img. This implicitly creates a bootable volume from volume snapshot, bv_1_vsnap, boot_vol2
  5. Delete vm_1, vm_2, vm_1_img. Now try to delete bv_1. This would fail as there is a dependent volume snapshot.

Shouldn't Nova do cleanup of these resources that are created implicitly?

edit retag flag offensive close merge delete


Can you provide more information like what your storage backend for Cinder is, if you have trouble with a volume that wont delete i'd refer to

omar-munoz gravatar imageomar-munoz ( 2015-03-06 17:29:52 -0600 )edit

I am using LVM as the storage backend.

nithya-ganesan gravatar imagenithya-ganesan ( 2015-03-09 04:45:10 -0600 )edit