[
https://issues.apache.org/jira/browse/CLOUDSTACK-4894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Federle resolved CLOUDSTACK-4894.
---------------------------------------
Resolution: Fixed
Assignee: Jessica Wang (was: Sonny Chhen)
Fix by existing commit:
commit ad51b8edfbb7e110db45368b118b55f89c7b7cba
Author: Jessica Wang <[email protected]>
Date: Fri Oct 25 13:48:38 2013 -0700
CLOUDSTACK-4966: UI: (1) detailView widget: extend detailView widget to
support destroy action that will close detai
(2)Destroy Instance action: add expunge option for root-admin and
domain-admin. When expunge is set to true, instanc
> [UI] destroyVm API: add support to force expunge the vm immediately
> --------------------------------------------------------------------
>
> Key: CLOUDSTACK-4894
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4894
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API, UI
> Affects Versions: 4.2.0
> Reporter: Alena Prokharchyk
> Assignee: Jessica Wang
> Fix For: 4.2.1
>
>
> When destroyVM API is called, the vm gets destroyed only in the DB. The
> actual expunge is being taken care later on by expunge thread (configured
> using expunge.interval and expunge.delay params). As we keep on getting the
> requests on adding a support for forceful expunge - when vm is expunged
> immediately after the call is made - it would make sense to introduce some
> flag to destroyVm command, controlling the behavior.
> So destroyVm will get new parameter - expunge (boolean, false by default).
> When true is passed as a value, the vm will be expunged right away.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
