We should NEVER delete records from the database.... and that's why "Expunged" seems a good candidate state, although I believe that state it's equivalent to state=Expunging, removed IS NOT NULL.
-NT Kind regards, Nuno Tavares Senior DevOps Infra Specialist LeaseWeb Technologies B.V. T: +31 20 316 0235 M: E: n.tava...@tech.leaseweb.com W: http://www.leaseweb.com Luttenbergweg 8, 1101 EC Amsterdam, Netherlands ________________________________________ From: Daan Hoogland [daan.hoogl...@gmail.com] Sent: Monday, February 22, 2016 8:21 AM To: dev Subject: Re: VM state = Expunging 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 make sense. Deabatable of course. On Mon, Feb 22, 2016 at 7:03 AM, Mike Tutkowski < mike.tutkow...@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 bit > odd (and front-ends that are waiting for the "Expunged" state to show up > won't see it). > > Thanks, > > -- > *Mike Tutkowski* > *Senior CloudStack Developer, SolidFire Inc.* > e: mike.tutkow...@solidfire.com > o: 303.746.7302 > Advancing the way the world uses the cloud > <http://solidfire.com/solution/overview/?video=play>*™* > -- Daan
