Mailing-List: contact cloudstack-users-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-users@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of
 magicloud.magiclouds@gmail.com designates 209.85.223.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <C66C814C1ABFA8449FF65CB44953A8B4012CBB65BCB4@SJCPMAILBOX01.citrite.net>
References: 
 <CABErt4fsmd2oy8KtZH4gDdmug=Y08Y88vRd85QHDDuAucLMZhg@mail.gmail.com>
	<CE52B3BAA8221C4A91FA40D3C8194ED2EBC5A4A27C@BANPMAILBOX01.citrite.net>
	<4D76A8A0-AD55-4F82-B5C1-23B353545362@citrix.com>
	<CABErt4dpwQw4JbwUBPGhBH+k71Zcf7NCMXHE6=-VpoSOe_7LPA@mail.gmail.com>
	<C66C814C1ABFA8449FF65CB44953A8B4012CBB65BCB4@SJCPMAILBOX01.citrite.net>
Date: Thu, 13 Sep 2012 09:34:10 +0800
Message-ID: 
 <CABErt4e=bZv_VvDzYSyee2c4PNwVtWJaS+G+z37YwTny0HL9Fg@mail.gmail.com>
Subject: Re: Error state (failed to create) VM cannot be destroyed.
From: Magicloud Magiclouds <magicloud.magiclouds@gmail.com>
To: cloudstack-users@incubator.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I see. Thank you.

On Wed, Sep 12, 2012 at 10:08 AM, Edison Su <Edison.su@citrix.com> wrote:
> 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 mark=
ed 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?
>> >> --
>> >> =E7=AB=B9=E5=AF=86=E5=B2=82=E5=A6=A8=E6=B5=81=E6=B0=B4=E8=BF=87
>> >> =E5=B1=B1=E9=AB=98=E5=93=AA=E9=98=BB=E9=87=8E=E4=BA=91=E9=A3=9E
>> >>
>> >> And for G+, please use magiclouds#gmail.com.
>>
>>
>>
>> --
>> =E7=AB=B9=E5=AF=86=E5=B2=82=E5=A6=A8=E6=B5=81=E6=B0=B4=E8=BF=87
>> =E5=B1=B1=E9=AB=98=E5=93=AA=E9=98=BB=E9=87=8E=E4=BA=91=E9=A3=9E
>>
>> And for G+, please use magiclouds#gmail.com.


--=20
=E7=AB=B9=E5=AF=86=E5=B2=82=E5=A6=A8=E6=B5=81=E6=B0=B4=E8=BF=87
=E5=B1=B1=E9=AB=98=E5=93=AA=E9=98=BB=E9=87=8E=E4=BA=91=E9=A3=9E

And for G+, please use magiclouds#gmail.com.