AttributeError in vmwareapi

Bug #1063885 reported by Christoph Lukas
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Invalid
Medium
Unassigned

Bug Description

We tried to installed the Folsom release (python-nova_2012.2-0ubuntu3~cloud0) and use an ESX Host as compute node.

Creating a new instance with:

nova boot --flavor 2 --image 6e4deabd-ccd6-412e-9bed-e3293f45a2db test1

We get the following error in nova-compute.log which can be fixed by the attached patch.

2012-10-08 13:01:45 TRACE nova.compute.manager [instance: 26679293-544b-4242-8af3-110fe2ec792d] Traceback (most recent call last):
2012-10-08 13:01:45 TRACE nova.compute.manager [instance: 26679293-544b-4242-8af3-110fe2ec792d] File "/usr/lib/python2.7/dist-packages/nova/compute/manager.p
y", line 743, in _spawn
2012-10-08 13:01:45 TRACE nova.compute.manager [instance: 26679293-544b-4242-8af3-110fe2ec792d] block_device_info)
2012-10-08 13:01:45 TRACE nova.compute.manager [instance: 26679293-544b-4242-8af3-110fe2ec792d] File "/usr/lib/python2.7/dist-packages/nova/virt/vmwareapi/dr
iver.py", line 132, in spawn
2012-10-08 13:01:45 TRACE nova.compute.manager [instance: 26679293-544b-4242-8af3-110fe2ec792d] self._vmops.spawn(context, instance, image_meta, network_in
fo)
2012-10-08 13:01:45 TRACE nova.compute.manager [instance: 26679293-544b-4242-8af3-110fe2ec792d] File "/usr/lib/python2.7/dist-packages/nova/virt/vmwareapi/vm
ops.py", line 101, in spawn
2012-10-08 13:01:45 TRACE nova.compute.manager [instance: 26679293-544b-4242-8af3-110fe2ec792d] vm_ref = self._get_vm_ref_from_the_name(instance.name)
2012-10-08 13:01:45 TRACE nova.compute.manager [instance: 26679293-544b-4242-8af3-110fe2ec792d] AttributeError: 'dict' object has no attribute 'name'

Tags: vmware
Revision history for this message
Christoph Lukas (christoph-lukas) wrote :
tags: added: vmware
Revision history for this message
Bob Shiflet (robert-k-shiflet) wrote :

Christoph - Wie gehts? Mein Deustche ist nicht so gut!

We are using a RHEL - ESXi configuration and ran into the same problem.

We had already applied a patch similar to the one that you have indicated.

Have you been able to actually deploy a VM.

We have run into an issue that when we try to deploy a VM the transfer of the VMDK never happens - sound familiar?

Revision history for this message
Russell Bryant (russellb) wrote :

Thanks for the patch! Please submit the patch through gerrit so we can get it merged.

http://wiki.openstack.org/HowToContribute

http://wiki.openstack.org/GerritWorkflow

Changed in nova:
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
Sean Dague (sdague) wrote :

moving to incomplete because we need Christoph as the original author to submit this to gerrit for it to be includible in openstack so that it clears the CLA.

Changed in nova:
status: Confirmed → Incomplete
Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote :

new vmware driver in grizzly was written from scratch. so you should not see this in grizzly

Changed in nova:
status: Incomplete → Fix Committed
Thierry Carrez (ttx)
Changed in nova:
status: Fix Committed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.