[
https://issues.apache.org/jira/browse/CLOUDSTACK-10337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Tutkowski reassigned CLOUDSTACK-10337:
-------------------------------------------
Assignee: Mike Tutkowski
> 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
> 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 in
> the same cluster 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)
