[
https://issues.apache.org/jira/browse/CLOUDSTACK-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13701955#comment-13701955
]
ASF subversion and git services commented on CLOUDSTACK-3393:
-------------------------------------------------------------
Commit 916a009d5d300d5621970a2ca29bd23e5d29fec3 in branch refs/heads/4.2 from
[~koushikd]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=916a009 ]
CLOUDSTACK-3393: Local disk recreated for stopped VM when started
Recreating local disk will result in cleanup of the old disk and this will lead
to data loss. So preventing this and bailing out with error. Once migration of
local disk is supported then another option is to migrate the existing disk to
the new local storage pool.
> Local disk recreated for stopped VM when started
> ------------------------------------------------
>
> Key: CLOUDSTACK-3393
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3393
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.1.0, 4.2.0
> Reporter: Koushik Das
> Assignee: Koushik Das
> Fix For: 4.2.0
>
>
> If a stopped VM using local storage (already created) is started and for some
> reasons it fails to start on the last host, the deployment planner picks up
> another host. In this scenario a new disk is created on the local storage
> pool associated with the new host and the old disk gets destroyed. This will
> result in data loss.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
