The backing VM corresponding to a volume is cloned during create volume
from another volume, snapshot or image. The backing VM is also cloned
during retype and backup restore. Currently, the target ESX host is
unset while calling vCenter CloneVM_Task API and hence the source ESX
host is used as the target. If the destination datastore returned by
the datastore selection logic is not accessible to the source host,
clone fails. This patch fixes the problem by setting the target ESX
host (returned by datastore selection logic) while invoking clone.
Conflicts: cinder/volume/drivers/vmware/vmdk.py
Closes-Bug: #1380602
Change-Id: I030d5ce6378fb70f7f98356114825abc12297687
(cherry picked from commit 9e590a6c854cec6df18630954734e4a4e0249a91)
Reviewed: https:/ /review. openstack. org/137537 /git.openstack. org/cgit/ openstack/ cinder/ commit/ ?id=0d60ddc7679 6e47f2921bdb51f c8174aa3800ab0
Committed: https:/
Submitter: Jenkins
Branch: stable/juno
commit 0d60ddc76796e47 f2921bdb51fc817 4aa3800ab0
Author: Vipin Balachandran <email address hidden>
Date: Wed Nov 19 16:08:45 2014 +0530
VMware: Set target ESX host for backing VM clone
The backing VM corresponding to a volume is cloned during create volume
from another volume, snapshot or image. The backing VM is also cloned
during retype and backup restore. Currently, the target ESX host is
unset while calling vCenter CloneVM_Task API and hence the source ESX
host is used as the target. If the destination datastore returned by
the datastore selection logic is not accessible to the source host,
clone fails. This patch fixes the problem by setting the target ESX
host (returned by datastore selection logic) while invoking clone.
Conflicts:
cinder/ volume/ drivers/ vmware/ vmdk.py
Closes-Bug: #1380602 0f7f98356114825 abc12297687 df18630954734e4 a4e0249a91)
Change-Id: I030d5ce6378fb7
(cherry picked from commit 9e590a6c854cec6