Cloud,  DevStack

Openstack Error_deleting statusünde ki Volume Silme

[stack@faopenstack devstack(keystone)]$ cinder delete 0731302a-6ada-4898-85b7-f5c4cf77fba8
Request to delete volume 0731302a-6ada-4898-85b7-f5c4cf77fba8 has been accepted.
[stack@faopenstack devstack(keystone)]$ cinder list
+--------------------------------------+----------------+------+------+-------------+----------+--------------------------------------+
| ID | Status | Name | Size | Volume Type | Bootable | Attached to |
+--------------------------------------+----------------+------+------+-------------+----------+--------------------------------------+
| 0731302a-6ada-4898-85b7-f5c4cf77fba8 | error_deleting | | 10 | lvmdriver-1 | true | |
| 6028ec46-cef4-471d-bdf1-ceb97e960ae0 | in-use | | 10 | lvmdriver-1 | true | d4890610-fddb-4870-af13-af48447b36fa |
| 6fcf85a5-70ac-4934-8c65-94029fa090e0 | in-use | | 10 | lvmdriver-1 | true | 81c93c74-c209-4d2b-8d13-ecc59ef3657e |
+--------------------------------------+----------------+------+------+-------------+----------+--------------------------------------+

Çözüm

  1. [stack@faopenstack devstack(keystone)]$ cinder reset-state –state available 0731302a-6ada-4898-85b7-f5c4cf77fba8
  2. [stack@faopenstack devstack(keystone)]$ mysql
  3. mysql> update volumes set deleted=1,status=’deleted’,deleted_at=now(),updated_at=now() where deleted=0 and id=’0731302a-6ada-4898-85b7-f5c4cf77fba8′;

2xVCP - Kubernetes & Openstack Administrator

One Comment

  • Onur Ozkan

    reset-state komutundan sonra volume’u cinder delete ile tekrar silmeyi deneyebilirsiniz. Oncesinde silinecek volume’e bagli herhangi bir volume-snapshot bulunmadigindan emin olmak lazim.

Bir cevap yazın

E-posta hesabınız yayımlanmayacak. Gerekli alanlar * ile işaretlenmişlerdir