cloudstack/engine
Mike Tutkowski e471a46a05 managed-storage: handle VM start in a new cluster on different host (#2656)
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.
2018-05-21 16:22:33 +05:30
..
api CLOUDSTACK-10290: allow config drives on primary storage for KVM (#2651) 2018-05-21 14:27:23 +05:30
components-api Updating pom.xml version numbers for release 4.11.1.0-SNAPSHOT 2018-02-26 16:57:48 +01:00
network Updating pom.xml version numbers for release 4.11.1.0-SNAPSHOT 2018-02-26 16:57:48 +01:00
orchestration managed-storage: handle VM start in a new cluster on different host (#2656) 2018-05-21 16:22:33 +05:30
schema CLOUDSTACK-9184: Fixes #2631 VMware dvs portgroup autogrowth (#2634) 2018-05-11 22:16:13 +05:30
service Updating pom.xml version numbers for release 4.11.1.0-SNAPSHOT 2018-02-26 16:57:48 +01:00
storage CLOUDSTACK-10290: allow config drives on primary storage for KVM (#2651) 2018-05-21 14:27:23 +05:30
pom.xml CLOUDSTACK-10290: allow config drives on primary storage for KVM (#2651) 2018-05-21 14:27:23 +05:30