You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Mike Tutkowski (JIRA)" <ji...@apache.org> on 2018/08/10 16:06:00 UTC
[jira] [Commented] (CLOUDSTACK-10337) Managed Storage: Check
cluster ID, not host ID, when starting up a VM in a new cluster
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16576493#comment-16576493 ]
Mike Tutkowski commented on CLOUDSTACK-10337:
---------------------------------------------
Merged: https://github.com/apache/cloudstack/pull/2656
> Managed Storage: Check cluster ID, not host ID, when starting up a VM in a new cluster
> --------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-10337
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10337
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server
> Affects Versions: 4.11.0.0
> Environment: All
> Reporter: Mike Tutkowski
> Assignee: Mike Tutkowski
> Priority: Major
> Fix For: 4.12.0.0
>
>
> Example: A VM that uses managed storage is stopped. The VM is then started on a different host in the same cluster. The Start operation fails.
> To get around this issue, you must either start the VM up on the same host or on a host in a different cluster.
> The reason is due to a slightly erroneous check in VolumeOrchestrator.prepare.
> To solve this issue, we should be checking if the cluster ID changes, not if the host ID changes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)