openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #03611
multinode diablo - debugging why a VM won't start up
Good morning,
I've installed Diablo from packages (from trunk) yesterday on Ubuntu 11.04 - and have a single instance setup working just fine for firing up instances, shutting them down, etc.
I then attempted to add a computing node to that setup, but have been unable to get instances to fire up on that remote node. euca-describe-instances shows it going past "scheduling" to "networking", but it doesn't get beyond that point. In the logs, I see the nova-compute attempt to create the node:
It talks with Glance, gets the instance details, and then makes a call to nova-network, where it seems to stall out.
2011-08-19 08:37:13,456 DEBUG nova.rpc [-] Making asynchronous call on network ... from (pid=1047) multicall /usr/lib/pymodules/python2.7/nova/rpc/amqp.py:462
2011-08-19 08:37:13,457 DEBUG nova.rpc [-] MSG_ID is c35f4791df754059b70f7351706db17f from (pid=1047) multicall /usr/lib/pymodules/python2.7/nova/rpc/amqp.py:465
After a little while (few seconds), I start to see this in the logs:
2011-08-19 08:37:57,136 INFO nova.compute.manager [-] Found instance 'instance-00000015' in DB but no VM. State=0, so setting state to shutoff.
2011-08-19 08:37:57,137 INFO nova.compute.manager [-] DB/VM state mismatch. Changing state from '0' to '5'
I'm using KVM, and the /etc/nova/nova.conf file is a replica of the one on the controller node. Other quirks of this setup include running it on a single NIC (eth0) and FlatDHCPNetworking.
(relevant pieces from nova.conf)
--network_manager=nova.network.manager.FlatDHCPManager
--flat_network_bridge=br100
--flat_injected=False
--flat_interface=eth0
--public_interface=eth0
While I see a br100 network interface (gets created for me) on the controller, I don't see one on the compute-only node (I've installed the packages nova-compute and nova-network). Do I need to create a br100 manually in /etc/network/interfaces?
Any suggestions on where I would look for additional logging/debugging information? It seems like something in failing in nova-network, but i'm not sure where to look for and see more detail.
-joe