You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/07/14 23:50:05 UTC

[jira] [Commented] (CLOUDSTACK-6595) Action event EVENT_VM_EXPUNGE is not generated when vm is expunged by the background expunge thread

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-6595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14061309#comment-14061309 ] 

ASF subversion and git services commented on CLOUDSTACK-6595:
-------------------------------------------------------------

Commit 4f0640dac4036d92bcda745c8fa80afcae5eae55 in cloudstack's branch refs/heads/master from [~alena1108]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4f0640d ]

CLOUDSTACK-6595: allow to expunge the vm when its in Error state, in addition to Expunging/Destroyed states


> 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)