cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Edison Su <Edison...@citrix.com>
Subject RE: Error state (failed to create) VM cannot be destroyed.
Date Wed, 12 Sep 2012 02:08:33 GMT
From the log, the destroyvm command is finished in about 5 seconds. After the destroyvm command
finished, then your vm will be marked as "expunging" state, as I said in previous mail, which
is expected. Your VM will be marked as removed in DB until expunge timeout happened.

> -----Original Message-----
> From: Magicloud Magiclouds [mailto:magicloud.magiclouds@gmail.com]
> Sent: Tuesday, September 11, 2012 12:00 AM
> To: cloudstack-users@incubator.apache.org
> Subject: Re: Error state (failed to create) VM cannot be destroyed.
> 
> +Nitin, it stays at that state and prevent the network related from
> deleting.
> +Edison, so it is OK to stay in this state before timeout? I thought
> things with a long timeout meant something was wrong.... Should it be
> done in a short time after the command was issued?
> 
> On Tue, Sep 11, 2012 at 2:50 PM, Edison Su <Edison.su@citrix.com> wrote:
> > There is an expunging timeout in global configuration, which controls
> how long the VM will stay in expunging state. If timeout, VM will be
> marked as removed in the database, thus won't show on the UI. By
> default, the timeout is one day.
> >
> > Sent from my iPhone
> >
> > On Sep 10, 2012, at 11:39 PM, "Nitin Mehta" <Nitin.Mehta@citrix.com>
> wrote:
> >
> >> Expunging is actually the last state. It should have been 'expunged'
> instead.
> >>
> >> -----Original Message-----
> >> From: Magicloud Magiclouds [mailto:magicloud.magiclouds@gmail.com]
> >> Sent: Tuesday, September 11, 2012 11:23 AM
> >> To: cloudstack-users@incubator.apache.org
> >> Subject: Error state (failed to create) VM cannot be destroyed.
> >>
> >> Hi,
> >>  CS3. Just creating a vm, and failed due to network misconfiguration.
> >> Then I was trying to delete the vm, it stuck on expunging. From
> management log, I saw:
> >>
> >> 2012-09-11 13:43:10,684 DEBUG [cloud.async.AsyncJobManagerImpl]
> >> (Job-Executor-20:job-34) Executing
> com.cloud.api.commands.DestroyVMCmd
> >> for job-34
> >> 2012-09-11 13:43:10,721 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> >> (Job-Executor-20:job-34) Destroying vm VM[User|i-2-1074-VM]
> >> 2012-09-11 13:43:10,721 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> >> (Job-Executor-20:job-34) Stopped called on VM[User|i-2-1074-VM] but
> the state is Error
> >> 2012-09-11 13:43:10,743 DEBUG [cloud.capacity.CapacityManagerImpl]
> >> (Job-Executor-20:job-34) VM state transitted from :Error to
> Expunging with event: DestroyRequestedvm's original host id: null new
> host id:
> >> null host id before state transition: null
> >> 2012-09-11 13:43:10,776 DEBUG [cloud.async.AsyncJobManagerImpl]
> >> (Job-Executor-20:job-34) Complete async job-34, jobStatus: 1,
> >> resultCode: 0, result:
> com.cloud.api.response.UserVmResponse@48f53518
> >> 2012-09-11 13:43:10,926 DEBUG [cloud.async.AsyncJobManagerImpl]
> >> (Job-Executor-20:job-34) Done executing
> >> com.cloud.api.commands.DestroyVMCmd for job-34
> >> 2012-09-11 13:43:15,708 DEBUG [cloud.async.AsyncJobManagerImpl]
> >> (catalina-exec-9:null) Async job-34 completed
> >>
> >>  What should I do?
> >> --
> >> 竹密岂妨流水过
> >> 山高哪阻野云飞
> >>
> >> And for G+, please use magiclouds#gmail.com.
> 
> 
> 
> --
> 竹密岂妨流水过
> 山高哪阻野云飞
> 
> And for G+, please use magiclouds#gmail.com.
Mime
View raw message