Re: VMs not Expunging

2014-11-26 Thread Kirk Kosinski
Hi, if the disks and storage are gone you can hack the database to force
them out of the system.  Just set the volumes for the affected VMs as
state = Expunged and removed = now() and hopefully CloudStack will be
able to expunge the VMs fully (i.e. they'll disappear from the UI).  Of
course be careful when doing anything in the db (take a backup first, etc.).

Best regards,
Kirk

On 11/25/2014 08:51 AM, Brent Clark wrote:
 Thanks for all the responses everyone.
 
 Version of CS = 4.2.1
 Status of Primary storage = unused, all VMs on local storage
 
 The VMs that wont expunge were on a CS host that doesnt exist anymore. The
 VMs were stored on local storage on that CS host. The VMs files dont exist
 anymore.
 
 -- Forwarded message --
 From: Kirk Kosinski kirkkosin...@gmail.com
 To: users@cloudstack.apache.org
 Cc:
 Date: Mon, 24 Nov 2014 22:20:20 -0800
 Subject: Re: VMs not Expunging
 Hi, Brent.  What version of CS is this, and what is the status of the
 primary storage for the VMs?  Were they on local storage (i.e. are the
 VM disks all gone along with the dead host)?
 
 Best regards,
 Kirk
 


Re: VMs not Expunging

2014-11-25 Thread Brent Clark
Thanks for all the responses everyone.

Version of CS = 4.2.1
Status of Primary storage = unused, all VMs on local storage

The VMs that wont expunge were on a CS host that doesnt exist anymore. The
VMs were stored on local storage on that CS host. The VMs files dont exist
anymore.

-- Forwarded message --
From: Kirk Kosinski kirkkosin...@gmail.com
To: users@cloudstack.apache.org
Cc:
Date: Mon, 24 Nov 2014 22:20:20 -0800
Subject: Re: VMs not Expunging
Hi, Brent.  What version of CS is this, and what is the status of the
primary storage for the VMs?  Were they on local storage (i.e. are the
VM disks all gone along with the dead host)?

Best regards,
Kirk

-- 
Brent S. Clark
Senior Cloud  Infrastructure Systems Engineer

2580 55th St.  |  Boulder, Colorado 80301
www.tendrilinc.com  |  blog http://www.tendrilinc.com/news-room/blog/
http://www.tendrilinc.com/

 
This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the sender.
Please note that any views or opinions presented in this email are solely those 
of the author and do not necessarily represent those of the company.
Finally, the recipient should check this email and any attachments for the 
presence of viruses.
The company accepts no liability for any damage caused by any virus transmitted 
by this email.


Re: VMs not Expunging

2014-11-22 Thread Fernandez, H.J.
Hi Brent,

It happened to me and just simply forced the expunge operation. You could also 
handle it via API adding a parameter “expunge=True” which will force the 
expunge operation to these machines.

Hector

Linkedin: 
linkedin.com/in/hector2fernandezhttps://www.linkedin.com/in/hector2fernandez
Twitter:  twitter.com/hectorj2fhttp://twitter.com/hectorj2f





On Nov 22, 2014, at 6:40 AM, Alireza Eskandari 
astro.alir...@yahoo.com.INVALIDmailto:astro.alir...@yahoo.com.INVALID wrote:

Hi Brent
I suggest you to change state of the VM to Stopped from database.
This action enables you to try destroy VM again fron UI.

Sent from Samsung Mobile.

div Original message /divdivFrom: Brent Clark 
bcl...@tendrilinc.commailto:bcl...@tendrilinc.com 
/divdivDate:22/11/2014  00:30  (GMT+03:30) /divdivTo: 
users@cloudstack.apache.orgmailto:users@cloudstack.apache.org 
/divdivSubject: VMs not Expunging /divdiv
/divHello, I have an issue were a number of vms are in Expunging state and
have been for days. The KVM host they lived on crashed and isnt coming
back. I had to force remove the host from the cluster. This left the vms in
the CloudStack Manager in a destroyed state. 24hrs later they moved to
Expunging state and have been there since. (~3days now)

From within the CloudStack manger, there is no option to do anything with
them because they are in Expunging state.

How do I get rid of these entries?

Thanks!

--
Brent S. Clark
Senior Cloud  Infrastructure Systems Engineer

2580 55th St.  |  Boulder, Colorado 80301
www.tendrilinc.comhttp://www.tendrilinc.com  |  blog 
http://www.tendrilinc.com/news-room/blog/
http://www.tendrilinc.com/


This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the sender.
Please note that any views or opinions presented in this email are solely those 
of the author and do not necessarily represent those of the company.
Finally, the recipient should check this email and any attachments for the 
presence of viruses.
The company accepts no liability for any damage caused by any virus transmitted 
by this email.



RE: VMs not Expunging

2014-11-21 Thread Michael Phillips
Check your expunge.delay and expunge.interval global settings. More than likely 
your expunge.interval setting is set high..

 Date: Fri, 21 Nov 2014 14:00:07 -0700
 Subject: VMs not Expunging
 From: bcl...@tendrilinc.com
 To: users@cloudstack.apache.org
 
 Hello, I have an issue were a number of vms are in Expunging state and
 have been for days. The KVM host they lived on crashed and isnt coming
 back. I had to force remove the host from the cluster. This left the vms in
 the CloudStack Manager in a destroyed state. 24hrs later they moved to
 Expunging state and have been there since. (~3days now)
 
 From within the CloudStack manger, there is no option to do anything with
 them because they are in Expunging state.
 
 How do I get rid of these entries?
 
 Thanks!
 
 -- 
 Brent S. Clark
 Senior Cloud  Infrastructure Systems Engineer
 
 2580 55th St.  |  Boulder, Colorado 80301
 www.tendrilinc.com  |  blog http://www.tendrilinc.com/news-room/blog/
 http://www.tendrilinc.com/
 
  
 This email and any files transmitted with it are confidential and intended 
 solely for the use of the individual or entity to whom they are addressed.
 If you have received this email in error please notify the sender.
 Please note that any views or opinions presented in this email are solely 
 those of the author and do not necessarily represent those of the company.
 Finally, the recipient should check this email and any attachments for the 
 presence of viruses.
 The company accepts no liability for any damage caused by any virus 
 transmitted by this email.
  

RE: VMs not Expunging

2014-11-21 Thread Alireza Eskandari
Hi Brent
I suggest you to change state of the VM to Stopped from database.
This action enables you to try destroy VM again fron UI. 

Sent from Samsung Mobile.

div Original message /divdivFrom: Brent Clark 
bcl...@tendrilinc.com /divdivDate:22/11/2014  00:30  (GMT+03:30) 
/divdivTo: users@cloudstack.apache.org /divdivSubject: VMs not 
Expunging /divdiv
/divHello, I have an issue were a number of vms are in Expunging state and
have been for days. The KVM host they lived on crashed and isnt coming
back. I had to force remove the host from the cluster. This left the vms in
the CloudStack Manager in a destroyed state. 24hrs later they moved to
Expunging state and have been there since. (~3days now)

From within the CloudStack manger, there is no option to do anything with
them because they are in Expunging state.

How do I get rid of these entries?

Thanks!

-- 
Brent S. Clark
Senior Cloud  Infrastructure Systems Engineer

2580 55th St.  |  Boulder, Colorado 80301
www.tendrilinc.com  |  blog http://www.tendrilinc.com/news-room/blog/
http://www.tendrilinc.com/


This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the sender.
Please note that any views or opinions presented in this email are solely those 
of the author and do not necessarily represent those of the company.
Finally, the recipient should check this email and any attachments for the 
presence of viruses.
The company accepts no liability for any damage caused by any virus transmitted 
by this email.