VMware: boot from volume exception

[Gary Kotton]

When the cinder volume is not on the same hos the following exception occurs.

2013-09-10 23:57:41.383 ERROR nova.compute.manager [req-4025681f-b5b6-49df-82b7-b16b7a988b3a demo demo] [instance: 7034fed5-10a7-4fcb-89d5-0a4bac46c768] Instance failed to spawn
2013-09-10 23:57:41.383 TRACE nova.compute.manager [instance: 7034fed5-10a7-4fcb-89d5-0a4bac46c768] Traceback (most recent call last):
2013-09-10 23:57:41.383 TRACE nova.compute.manager [instance: 7034fed5-10a7-4fcb-89d5-0a4bac46c768] File "/opt/stack/nova/nova/compute/manager.py", line 1416, in _spawn
2013-09-10 23:57:41.383 TRACE nova.compute.manager [instance: 7034fed5-10a7-4fcb-89d5-0a4bac46c768] block_device_info)
2013-09-10 23:57:41.383 TRACE nova.compute.manager [instance: 7034fed5-10a7-4fcb-89d5-0a4bac46c768] File "/opt/stack/nova/nova/virt/vmwareapi/driver.py", line 605, in spawn
2013-09-10 23:57:41.383 TRACE nova.compute.manager [instance: 7034fed5-10a7-4fcb-89d5-0a4bac46c768] admin_password, network_info, block_device_info)
2013-09-10 23:57:41.383 TRACE nova.compute.manager [instance: 7034fed5-10a7-4fcb-89d5-0a4bac46c768] File "/opt/stack/nova/nova/virt/vmwareapi/vmops.py", line 446, in spawn
2013-09-10 23:57:41.383 TRACE nova.compute.manager [instance: 7034fed5-10a7-4fcb-89d5-0a4bac46c768] self._default_root_device)
2013-09-10 23:57:41.383 TRACE nova.compute.manager [instance: 7034fed5-10a7-4fcb-89d5-0a4bac46c768] File "/opt/stack/nova/nova/virt/vmwareapi/volumeops.py", line 461, in attach_root_volume
2013-09-10 23:57:41.383 TRACE nova.compute.manager [instance: 7034fed5-10a7-4fcb-89d5-0a4bac46c768] device = self._get_vmdk_backed_disk_device(vm_ref, data)
2013-09-10 23:57:41.383 TRACE nova.compute.manager [instance: 7034fed5-10a7-4fcb-89d5-0a4bac46c768] File "/opt/stack/nova/nova/virt/vmwareapi/volumeops.py", line 391, in _get_vmdk_backed_disk_device
2013-09-10 23:57:41.383 TRACE nova.compute.manager [instance: 7034fed5-10a7-4fcb-89d5-0a4bac46c768] raise volume_util.StorageError(_("Unable to find volume"))
2013-09-10 23:57:41.383 TRACE nova.compute.manager [instance: 7034fed5-10a7-4fcb-89d5-0a4bac46c768] StorageError: Unable to find volume
2013-09-10 23:57:41.383 TRACE nova.compute.manager [instance: 7034fed5-10a7-4fcb-89d5-0a4bac46c768]

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/46027

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/46027
Committed: http://github.com/openstack/nova/commit/dd52437e0a64e58400c1d0e828a99b3334661354
Submitter: Jenkins
Branch: master

commit dd52437e0a64e58400c1d0e828a99b3334661354
Author: Gary Kotton <email address hidden>
Date: Wed Sep 11 01:02:06 2013 -0700

    VMware: fix bug with booting from volume

    When booting from volume ensure that the volume is on the same
    datastore as the instance being booted.

    Fixes bug 1223709

    Change-Id: Iddb70cdd7e358c401ef4f0b4d9e66b9655c2feeb