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/11 13:47:05 UTC

[jira] [Commented] (CLOUDSTACK-7099) Volume snapshot is not getting backed up

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

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

Commit 00778de96eb9f47a34bac79dc5175d16d71df194 in cloudstack's branch refs/heads/master from [~likithas]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=00778de ]

CLOUDSTACK-7099. Volume snapshot is not getting backed up.
Correctly inject ConfigDao into SnapshotStateListener.


> Volume snapshot is not getting backed up
> ----------------------------------------
>
>                 Key: CLOUDSTACK-7099
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7099
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Snapshot
>    Affects Versions: 4.5.0
>            Reporter: Likitha Shetty
>            Assignee: Likitha Shetty
>            Priority: Critical
>             Fix For: 4.5.0
>
>
> While trying to snapshot a volume, the volume snapshot is not backed up and it remains in 'Allocated' state.
> As a result of the fix made to resolve [https://issues.apache.org/jira/browse/CLOUDSTACK-3272], ConfigDao is not being injected into SnapshotStateListener which results in an NPE. And this causes the snapshot process to fail .



--
This message was sent by Atlassian JIRA
(v6.2#6252)