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

ASF GitHub Bot commented on CLOUDSTACK-9553:
--------------------------------------------

GitHub user yvsubhash opened a pull request:

    https://github.com/apache/cloudstack/pull/1714

    CLOUDSTACK-9553 Usage event is not getting recorded for snapshots in …

    …a specific scenario

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/yvsubhash/cloudstack CLOUDSTACK-9553

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/1714.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1714
    
----
commit 488711ba07afab4918b0a201c35ecff70e9e29e5
Author: subhash_y <venkata.yedugun...@accelerite.com>
Date:   2016-09-22T07:29:07Z

    CLOUDSTACK-9553 Usage event is not getting recorded for snapshots in a 
specific scenario

----


> Usage event is not getting recorded for snapshots in a specific scenario
> ------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9553
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9553
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Usage
>    Affects Versions: 4.9.0
>         Environment: vmware 4.5.1
>            Reporter: subhash yedugundla
>             Fix For: Future
>
>
> 1. Create a scheduled snapshot of the volume
> 2. Delete the snapshot schedule before the run of the usage job for the day. 
> 3. The usage job completes successfully but there is a error message "post 
> process snapshot failed"
> 4. The snapshot.create event is captured in the event table, but not in the 
> usage event table



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to