[
https://issues.apache.org/jira/browse/CLOUDSTACK-6595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14064679#comment-14064679
]
ASF subversion and git services commented on CLOUDSTACK-6595:
-------------------------------------------------------------
Commit 92d1428c480d013cc153b19b62a9a130258d1504 in cloudstack's branch
refs/heads/4.4 from [~alena1108]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=92d1428 ]
CLOUDSTACK-6595: allow to expunge the vm when its in Error state, in addition
to Expunging/Destroyed states
(cherry picked from commit 822b38761f1655ef3d5d3648985a197f5c2c1262)
> Action event EVENT_VM_EXPUNGE is not generated when vm is expunged by the
> background expunge thread
> ---------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-6595
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6595
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.4.0
> Reporter: Alena Prokharchyk
> Assignee: Kelven Yang
> Priority: Critical
> Fix For: 4.4.0
>
>
> When expungeVm is called using client API, EVENT_VM_EXPUNGE event is
> generated.
> When vm is destroyed through the API, but expunged by the background expunge
> thread, the event is missing. The event should be generated regardless of
> which way the expunge was triggered.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
