Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAGQtxvbwS9NpQt37VWLj+kg+YvgXqW8cpQMO9ChbtuRbNVK=LQ@mail.gmail.com>
References: 
 <CACOnxChoZ6jfieUeiBGo7KTFN_VK5ePbQ_XCLpC5nLEYeJxPMg@mail.gmail.com>
	<CAGQtxvbwS9NpQt37VWLj+kg+YvgXqW8cpQMO9ChbtuRbNVK=LQ@mail.gmail.com>
Date: Mon, 22 Feb 2016 14:20:59 +0530
Message-ID: 
 <CAB6y=04M22jGGpHpiGmAWMdmX9JuRVU-6s8_+QoXUzz3NgtyUg@mail.gmail.com>
Subject: Re: VM state = Expunging
From: Sanjeev N <sanjeev@apache.org>
To: dev@cloudstack.apache.org
Content-Type: multipart/alternative; boundary=047d7b86dd2c93020e052c57ee30

--047d7b86dd2c93020e052c57ee30
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Expunging is the final state of the vm. We don't have expunged state.

On Mon, Feb 22, 2016 at 12:51 PM, Daan Hoogland <daan.hoogland@gmail.com>
wrote:

> I ran into that as well, a while ago. IMNSHO the VM record should be
> deleted after the state expunging, so a state of expunged would never mak=
e
> sense. Deabatable of course.
>
> On Mon, Feb 22, 2016 at 7:03 AM, Mike Tutkowski <
> mike.tutkowski@solidfire.com> wrote:
>
> > Hi,
> >
> > Is anyone able to confirm that when you delete and expunge a VM in 4.9
> that
> > the state finishes with "Expunging" instead of "Expunged".
> >
> > I don't think it really "harms" much as the removed column is populated
> > (so, for example, the GUI doesn't show these VMs), but it does seem a b=
it
> > odd (and front-ends that are waiting for the "Expunged" state to show u=
p
> > won't see it).
> >
> > Thanks,
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkowski@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the cloud
> > <http://solidfire.com/solution/overview/?video=3Dplay>*=E2=84=A2*
> >
>
>
>
> --
> Daan
>

--047d7b86dd2c93020e052c57ee30--