Removed volumes and instances from database are being counted.

asked 2016-04-28 05:39:36 -0500

animaletdesequia gravatar image

We're having some troubles deploying Kilo on a system with 3 controllers and 3 computes, through mirantis fuel 7.0. The problems involve creation and attaching of volumes, specially the ones stored on a NetApp SAN. As a result, I had to delete some stuck volumes and instances through accessing to cinder and nova databases and deleting files from instances, volumes, volumes_admin_metadata, volume_attachment and volume_glance_metadata.

The problem is, the volume count on the "Overview" for the project still counts those disappeared volumes and instances, so I'd like to know what part of the database that information is being read and how to correct it / synchronize it.

Also I't like to know how to remove the phisical LVM corresponding to those volumes, since they still show up when I do an "lsblk" on the controller that was storing them.


edit retag flag offensive close merge delete



For what it's worth, I have this same issue. It is a nightmare. If you delete an image that failed to launch, the resources are leaked. I have not seen a cogent answer how to deal with it.

tiger gravatar imagetiger ( 2017-04-27 17:35:31 -0500 )edit

We are also facing the same issue with Volume deleted from database .Were you able to fix this .If yes can you please tell us how it was done

Deepa gravatar imageDeepa ( 2018-01-18 01:42:21 -0500 )edit