nova compute won't restart using vcdriver after vcenter rebuild

asked 2014-04-25 14:40:30 -0500

scarecrow gravatar image

I had a compute node pionted to a vCenter server with a 3-node host cluster and for various reasons, I had to rebuild me vcenter server and re-add my ESXi hosts. Now however, when I attempt to restart my nova-compute node using the vcdriver, with the IP settings updated, it won't start, giving me an error in the logs:

TRACE nova.openstack.common.threadgroup NotFound: The resource domain-c33(RG01-01) does not exist

However, in the new vCenter I have re-created that exact cluster name (RG01-01). Is there something in the bowels of OS in the database or something that is choking because "domain-c33" is dynamically generated based on something from the previous incarnation of vCenter? Any way to fix that or do I have to rip-out this nova-compute node an rebuild?

edit retag flag offensive close merge delete


I have installed 1 openstack controller and 2 KVM compute nodes and 1 dedicated compute node for managing VMware vcenter server. (vCenter 5.5 manages two ESXi 5.5 hosts). Note: Using Openstack Havana and Ubuntu 12.04.4

am able to create instance in KVM compute nodes using openstack dashboard and the instance are working fine.

i recently integrated VMware vcenter 5.5 to openstack and am able to see VMware vcenter cluster details in openstack dashboard in the hypervisor tab Reference link used for integration: .

I also uploaded vmdk images to glance, which is also visible in openstack dashboard images tab


When i deploy an instance using vmdk image from openstack dashboard the instance is getting deployed in KVM compute nodes rather than VMware vCenter cluster.

Please clarify how can i direct openstack dashboard to deploy the vmdk instance in VMware ...(more)

kamal gravatar imagekamal ( 2014-05-08 22:23:23 -0500 )edit