Chandan Purushothama created CLOUDSTACK-2157:
------------------------------------------------
Summary: On VMWare ESXi host deployment: Expunged VMs are not
getting cleaned up from the host
Key: CLOUDSTACK-2157
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2157
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server
Affects Versions: 4.2.0
Reporter: Chandan Purushothama
Priority: Critical
Fix For: 4.2.0
Attachments: VMsOnVCenter.PNG
===========
Observations:
===========
mysql> select id,name,instance_name,state,created,removed from vm_instance
where state="Expunging";
+----+--------------------------------------+------------------+-----------+---------------------+---------------------+
| id | name | instance_name | state |
created | removed |
+----+--------------------------------------+------------------+-----------+---------------------+---------------------+
| 1 | s-1-SYSVMTMPL | s-1-SYSVMTMPL | Expunging |
2013-04-19 20:40:55 | 2013-04-22 00:50:14 |
| 2 | v-2-SYSVMTMPL | v-2-SYSVMTMPL | Expunging |
2013-04-19 20:40:56 | 2013-04-22 00:50:50 |
| 4 | r-4-SYSVMTMPL | r-4-SYSVMTMPL | Expunging |
2013-04-19 21:34:01 | 2013-04-22 01:01:48 |
| 5 | Atoms-VM-2 | i-3-5-SYSVMTMPL | Expunging |
2013-04-20 21:56:40 | 2013-04-20 22:01:45 |
| 9 | r-9-SYSVMTMPL | r-9-SYSVMTMPL | Expunging |
2013-04-22 01:02:53 | 2013-04-22 01:13:11 |
| 10 | r-10-SYSVMTMPL | r-10-SYSVMTMPL | Expunging |
2013-04-22 01:13:11 | 2013-04-22 01:39:47 |
| 11 | r-11-SYSVMTMPL | r-11-SYSVMTMPL | Expunging |
2013-04-22 01:41:36 | 2013-04-22 02:16:02 |
| 12 | a2763995-78be-4477-9e24-b89970f60ce7 | i-3-12-SYSVMTMPL | Expunging |
2013-04-22 02:00:48 | 2013-04-22 02:03:22 |
+----+--------------------------------------+------------------+-----------+---------------------+---------------------+
8 rows in set (0.00 sec)
mysql> select * from configuration where name like "%expunge%";
+----------+----------+---------------+------------------+-------+--------------------------------------------------------------------------------------------------------------------------------------------+
| category | instance | component | name | value | description
|
+----------+----------+---------------+------------------+-------+--------------------------------------------------------------------------------------------------------------------------------------------+
| Advanced | DEFAULT | UserVmManager | expunge.delay | 60 | Determines
how long (in seconds) to wait before actually expunging destroyed vm. The
default value = the default value of expunge.interval |
| Advanced | DEFAULT | UserVmManager | expunge.interval | 60 | The interval
(in seconds) to wait before running the expunge thread.
|
| Advanced | DEFAULT | UserVmManager | expunge.workers | 1 | Number of
workers performing expunge
|
+----------+----------+---------------+------------------+-------+--------------------------------------------------------------------------------------------------------------------------------------------+
3 rows in set (0.13 sec)
mysql> select * from configuration where name like "%storage.clean%";
+----------+----------+----------------+--------------------------+-------+------------------------------------------------------------------------------+
| category | instance | component | name | value |
description |
+----------+----------+----------------+--------------------------+-------+------------------------------------------------------------------------------+
| Advanced | DEFAULT | StorageManager | storage.cleanup.enabled | true |
Enables/disables the storage cleanup thread. |
| Advanced | DEFAULT | StorageManager | storage.cleanup.interval | 60 | The
interval (in seconds) to wait before running the storage cleanup thread. |
+----------+----------+----------------+--------------------------+-------+------------------------------------------------------------------------------+
2 rows in set (0.00 sec)
I will attach the screenshot taken on the VCenter.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
