大网数据广告活动
服务器运维问答

How to completely remove volumes/instances from OpenStack Kilo database

· 52CE 我爱测

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…

问题原文

原帖链接 · animaletdesequia · CC BY-SA 3.0

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.

Thanks

已采纳解答

原帖链接 · Sum1sAdmin · CC BY-SA 3.0

I think you are using a multi backed cinder that can create volumes by using the netapp and lvm drivers - sometimes volumes can become stuck in any type of status 'create, extend, snapshot, delete etc. there is already a cli and horizon tool for resetting the status of stuck volumes, since you can't delete a volume that is stuck at a different status:

cinder reset-state --state available uuid

as for where the LVM is - it will be on the server which you installed the cinder role: from the fuel server

fuel role list

and then ssh onto the cinder node and look at lvm -v

if you don't intend you use the LVM driver (it's a reference driver so you can see how storage as a service works) then make sure to remove reference to the LVM driver in your cinder.conf.

you shouldn't have to go into the database to remove infrastructure, but it is necessary some times.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2016-04-28)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。