Ask Your Question

scarecrow's profile - activity

2015-11-17 22:47:10 -0500 received badge  Famous Question (source)
2014-10-16 03:56:24 -0500 received badge  Notable Question (source)
2014-05-12 00:29:11 -0500 received badge  Popular Question (source)
2014-04-25 14:40:30 -0500 asked a question nova compute won't restart using vcdriver after vcenter rebuild

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?

2014-04-10 05:27:14 -0500 received badge  Famous Question (source)
2014-03-31 01:27:46 -0500 received badge  Notable Question (source)
2014-03-14 09:12:24 -0500 received badge  Famous Question (source)
2014-02-28 10:30:23 -0500 received badge  Enthusiast
2014-02-21 18:03:14 -0500 received badge  Popular Question (source)
2014-02-20 03:45:55 -0500 received badge  Notable Question (source)
2014-02-17 17:28:48 -0500 commented answer Deleted VMs still showing in nova - Dashboard usage now out-of-sync

And I'll just add that I'm seeing this on 2 of the 3 KVM nodes that we have.

2014-02-17 17:27:33 -0500 commented answer Deleted VMs still showing in nova - Dashboard usage now out-of-sync

Anybody have any ideas on why virsh is successfully terminating the VM but the controller is not? The controller goes into a brief state of "deleting" for the instances task state , but the VM always stays ACTIVE and the only way to kill it is to hack the database?

2014-02-14 15:44:09 -0500 received badge  Popular Question (source)
2014-02-14 14:13:45 -0500 commented answer Deleted VMs still showing in nova - Dashboard usage now out-of-sync

Thanks for the pointer. I had completely missed this post: https://ask.openstack.org/en/question/494/how-to-reset-incorrect-quota-count/ Ok, so now that that's fixed, does anyon have any insight on Question 2)? I can re-post as another question if that is more appropriate.

2014-02-14 10:16:50 -0500 commented question Ubuntu Cloud Image: Key Injection

Do you have the nova-api-metadata service installed on the compute node which is using the VMwareESXiDriver?

2014-02-13 17:35:55 -0500 asked a question Deleted VMs still showing in nova - Dashboard usage now out-of-sync

For some reason after fixing some other issues on two KVM nodes, when I create a new instance and delete it using the "nova delete <uuid>" command, the VM is removed on the KVM node ("virsh list" comes up empty), but the controller node still shows it active when issuing the "nova list" command.

I've been able to go directly to the database and set all of the state params (vm_state, task_state, and deleted) to "deleted", NULL, and 0, respectively etc from the instances table. That successfully stopped them from showing up when running "nova list".

However, after doing that a few times, now horizon shows that all of my instance quota is used up and I cannot spawn any more VMs.

So: 1) How do I fix horizon so it accurately shows my running VMs? How can I get it to re-read the instances tables and update the "quota_usages" tables or am I going to have to manually update that.

2) Any ideas on why the compute node is successfully stopping the VM but the controller node is not getting updated or updating its DB.

The only log I have to go by at the moment on is this entry on the nova-compute node:

nova-compute.log.1:2014-02-12 15:21:14.306 47313 ERROR nova.network.api [req-c361a981-2a0e-4e70-b581-789169f87455 81fa9eb39aad4ec4bab77cd4c44664de 5a4e09f14dec4361870c1756edb28a45] [instance: 21c6fb58-c7d2-4602-bf8e-c7c282c9b3ec] Failed storing info cache
nova-compute.log.1:2014-02-12 15:21:16.052 47313 ERROR nova.virt.driver [-] Exception dispatching event <nova.virt.event.LifecycleEvent object at 0x3e71d10>: Version 1.9 of Instance is not supported
nova-compute.log.1:2014-02-12 15:21:16.728 47313 ERROR nova.openstack.common.rpc.amqp [req-c361a981-2a0e-4e70-b581-789169f87455 81fa9eb39aad4ec4bab77cd4c44664de 5a4e09f14dec4361870c1756edb28a45] Exception during message handling

Any ideas would be appreciated.

2014-02-07 19:05:15 -0500 answered a question cloud-init not pulling ssh key from metadata service on VMware

Finally figured this out. After installing cloud-init inside my Ubuntu image I needed to enable the Ec2 as a datasource in the /etc/cloud/cloud.cfg.d/90_dpkg.cfg file by running "dpkg-reconfigure cloud-init" and selecting EC2 as a datasource.

2014-02-07 16:09:27 -0500 asked a question cloud-init not pulling ssh key from metadata service on VMware

I am testing the Havana release with a mix of compute nodes, KVM and VMware using the VCDriver on one of the compute nodes. I can finally get instances to launch on both KVM and VMware nodes and even get block storage working. However, I can't get public-key injection to work on a custom imported vmdk image that contains the cloud-init package. The cloud Ubuntu image on KVM works fine.

In the boot log, it shows:

cloud-init start running: Fri, 07 Feb 2014 15:32:08 +0000. up 13.65 seconds no instance data found in start

In the cloud-init.log it shows:

2014-02-07 08:32:08,517 - __init__.py[DEBUG]: Did not find data source. searched classes: ['DataSourceNoCloudNet', 'DataSourceConfigDriveNet', 'DataSourceAzureNet', 'DataSourceOVFNet', 'DataSourceMAAS']

However, I can reach the metadata service running on the VMware driver compute node:

$ curl http://169.254.169.254/ 1.0 2007-01-19 2007-03-01 2007-08-29 2007-10-10 2007-12-15 2008-02-01 2008-09-01 2009-04-04 latest

So I'm not sure why this particular image is not able to pull the metadata? Is there some post cloud-init installation configuration that needs to be set in my custom image?