cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-8320) Upon a failed migration, a dummy volume is created which remains in 'Expunging' state.
Date Fri, 17 Apr 2015 14:06:59 GMT

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

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

Commit 326bb3e0a4d876b38d78b7f7bebe0f6a08863866 in cloudstack's branch refs/heads/4.5 from
[~likithas]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=326bb3e ]

CLOUDSTACK-8320. Upon a failed migration, a dummy volume is created which remains in 'Expunging'
state.

Set destination volume path as NULL while duplicating volume during migration.
If migration fails, destination volume will be marked as removed. And if migration succeeds,
volume path will be rightly updated.

(cherry picked from commit d30d5644bb59898ac60884280bd0767bf429ede8)
Signed-off-by: Rohit Yadav <rohit.yadav@shapeblue.com>


> 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