cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Likitha Shetty (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-8320) Upon a failed migration, a dummy volume is created which remains in 'Expunging' state.
Date Thu, 12 Mar 2015 08:05:38 GMT

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

Likitha Shetty commented on CLOUDSTACK-8320:
--------------------------------------------

Stale volumes will be left behind only in case of a failure during migration. Also, we can
easily workaround this issue by updating the state to 'Expunged' and marking it as removed.
So I don't think its critical enough to go into 4.5 at this stage of the release. 

> Upon a failed migration, a dummy volume is created which remains in 'Expunging' state.
> --------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-8320
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8320
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Volumes
>            Reporter: Likitha Shetty
>            Assignee: Likitha Shetty
>             Fix For: 4.6.0
>
>
> During volume migration, a volume is created in CloudStack DB to track the destination
volume. In case of a failure in migration, the destination volume's state is updated to 'Expunging'
and is never marked as removed. Hence an additional volume which doesn't exist on storage
volume counts against the user's volume limit.



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

Mime
View raw message