cloudstack/plugins/hypervisors
Likitha Shetty c8a437b782 BUG-ID: CLOUDSTACK-7102. Volume migration fails with 'VM i-2-3-VM does not exist in VMware datacenter' expection.
Look for a VM in vCenter based on both the vCenter name and CS internal name (required in case 'vm.instancename.flag' is enabled).
During Attach Volume and Volume Migration, for lookup and other operations use VM's name as obtained from vCenter instead of using the name set in the agent command.

(cherry picked from commit b8fdda0a34)
Signed-off-by: Rohit Yadav <rohit.yadav@shapeblue.com>
2015-02-02 13:51:04 +05:30
..
baremetal CLOUDSTACK-8088: VM scale up is failing in vmware with Unable to execute ScaleVmCommand due to java.lang.NullPointerException 2015-01-18 17:28:17 +05:30
hyperv CLOUDSTACK-8088: VM scale up is failing in vmware with Unable to execute ScaleVmCommand due to java.lang.NullPointerException 2015-01-18 17:28:17 +05:30
kvm LibvirtComputingResource: Expose KVMStoragePoolManager 2015-01-23 02:44:08 -07:00
ovm CLOUDSTACK-8088: VM scale up is failing in vmware with Unable to execute ScaleVmCommand due to java.lang.NullPointerException 2015-01-18 17:28:17 +05:30
simulator CLOUDSTACK-8088: VM scale up is failing in vmware with Unable to execute ScaleVmCommand due to java.lang.NullPointerException 2015-01-18 17:28:17 +05:30
ucs Improve the handling of the findbug exclude files 2014-09-03 10:41:22 +02:00
vmware BUG-ID: CLOUDSTACK-7102. Volume migration fails with 'VM i-2-3-VM does not exist in VMware datacenter' expection. 2015-02-02 13:51:04 +05:30
xenserver CLOUDSTACK-8160: use preferable protocols 2015-01-21 18:02:58 +05:30