VMware: volume attachment fails with exception

[Gary Kotton]

Whan attaching to a volume the following exception is returned:

2013-08-04 05:54:10.326 ERROR nova.openstack.common.rpc.amqp [req-f8ec0f25-c8db-4e2f-9bc9-fd087688ec0d demo demo] Exception during message handling
2013-08-04 05:54:10.326 TRACE nova.openstack.common.rpc.amqp Traceback (most recent call last):
2013-08-04 05:54:10.326 TRACE nova.openstack.common.rpc.amqp File "/opt/stack/nova/nova/openstack/common/rpc/amqp.py", line 421, in _process_data
2013-08-04 05:54:10.326 TRACE nova.openstack.common.rpc.amqp **args)
2013-08-04 05:54:10.326 TRACE nova.openstack.common.rpc.amqp File "/opt/stack/nova/nova/openstack/common/rpc/dispatcher.py", line 172, in dispatch
2013-08-04 05:54:10.326 TRACE nova.openstack.common.rpc.amqp result = getattr(proxyobj, method)(ctxt, **kwargs)
2013-08-04 05:54:10.326 TRACE nova.openstack.common.rpc.amqp File "/opt/stack/nova/nova/exception.py", line 100, in wrapped
2013-08-04 05:54:10.326 TRACE nova.openstack.common.rpc.amqp temp_level, payload)
2013-08-04 05:54:10.326 TRACE nova.openstack.common.rpc.amqp File "/opt/stack/nova/nova/exception.py", line 77, in wrapped
2013-08-04 05:54:10.326 TRACE nova.openstack.common.rpc.amqp return f(self, context, *args, **kw)
2013-08-04 05:54:10.326 TRACE nova.openstack.common.rpc.amqp File "/opt/stack/nova/nova/compute/manager.py", line 230, in decorated_function
2013-08-04 05:54:10.326 TRACE nova.openstack.common.rpc.amqp pass
2013-08-04 05:54:10.326 TRACE nova.openstack.common.rpc.amqp File "/opt/stack/nova/nova/compute/manager.py", line 216, in decorated_function
2013-08-04 05:54:10.326 TRACE nova.openstack.common.rpc.amqp return function(self, context, *args, **kwargs)
2013-08-04 05:54:10.326 TRACE nova.openstack.common.rpc.amqp File "/opt/stack/nova/nova/compute/manager.py", line 245, in decorated_function
2013-08-04 05:54:10.326 TRACE nova.openstack.common.rpc.amqp return function(self, context, *args, **kwargs)
2013-08-04 05:54:10.326 TRACE nova.openstack.common.rpc.amqp File "/opt/stack/nova/nova/compute/manager.py", line 3431, in attach_volume
2013-08-04 05:54:10.326 TRACE nova.openstack.common.rpc.amqp context, instance, mountpoint)
2013-08-04 05:54:10.326 TRACE nova.openstack.common.rpc.amqp File "/opt/stack/nova/nova/compute/manager.py", line 3426, in attach_volume
2013-08-04 05:54:10.326 TRACE nova.openstack.common.rpc.amqp mountpoint, instance)
2013-08-04 05:54:10.326 TRACE nova.openstack.common.rpc.amqp File "/opt/stack/nova/nova/compute/manager.py", line 3468, in _attach_volume
2013-08-04 05:54:10.326 TRACE nova.openstack.common.rpc.amqp connector)
2013-08-04 05:54:10.326 TRACE nova.openstack.common.rpc.amqp File "/opt/stack/nova/nova/compute/manager.py", line 3458, in _attach_volume
2013-08-04 05:54:10.326 TRACE nova.openstack.common.rpc.amqp mountpoint)
2013-08-04 05:54:10.326 TRACE nova.openstack.common.rpc.amqp File "/opt/stack/nova/nova/virt/vmwareapi/driver.py", line 307, in attach_volume
2013-08-04 05:54:10.326 TRACE nova.openstack.common.rpc.amqp mountpoint)
2013-08-04 05:54:10.326 TRACE nova.openstack.common.rpc.amqp File "/opt/stack/nova/nova/virt/vmwareapi/volumeops.py", line 137, in attach_volume
2013-08-04 05:54:10.326 TRACE nova.openstack.common.rpc.amqp raise exception.InstanceNotFound(instance_id=instance_name)
2013-08-04 05:54:10.326 TRACE nova.openstack.common.rpc.amqp InstanceNotFound: Instance instance-00000001 could not be found.
2013-08-04 05:54:10.326 TRACE nova.openstack.common.rpc.amqp

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/40105
Committed: http://github.com/openstack/nova/commit/7fe0934e72091d63543f9fe680835bdcf81a054e
Submitter: Jenkins
Branch: master

commit 7fe0934e72091d63543f9fe680835bdcf81a054e
Author: Gary Kotton <email address hidden>
Date: Sun Aug 4 06:26:15 2013 -0700

    VMware: use VM uuid for volume attach and detach

    When using the instance name an exception occurs. The problem is due
    to the way in which the VM's are named on vCenter. On vCenter the name
    of a VM is actually the nova uuid - hence all intercations with the VM
    should be done by the uuid. The problem here is that the name was used.

    Fixes bug: 1208173

    Change-Id: Iefe1584ee1ded403815cf0ca1fb5206ceadd3e55