Open Stack

Hello,

I have two node OpenStack setup, one controller-node (hostname: bodega) and one compute-node (hostname: sonoma).  I am running nova-network in a  single host mode, nova-network running on controller-node only.  During the creation of a VM instance I am running into an error due to "RPC message timeout".

I see numerous log messages that seem to raise red flags (for me).

1. Why is nova-network allocating floating IP address when I did not set it as such in nova.conf file:

2012-11-18 15:50:29 DEBUG nova.network.manager [req-f2b4df1f-6c29-48dc-991b-93fb5eb29d08 ce016bb05df949ebbafcc7c165359d7c ce1e819636744dc680fa5515f6475e87] [instance: 4e80964e-5bd1-4df4-a517-223c79d55517] floating IP allocation for instance |%s| from (pid=1375) allocate_for_instance /usr/lib/python2.7/dist-packages/nova/network/manager.py:315
2012-11-18 15:50:29 DEBUG nova.network.manager [req-f2b4df1f-6c29-48dc-991b-93fb5eb29d08 ce016bb05df949ebbafcc7c165359d7c ce1e819636744dc680fa5515f6475e87] [instance: 4e80964e-5bd1-4df4-a517-223c79d55517] network allocations from (pid=1375) allocate_for_instance /usr/lib/python2.7/dist-packages/nova/network/manager.py:977
2012-11-18 15:50:29 DEBUG nova.network.manager [req-f2b4df1f-6c29-48dc-991b-93fb5eb29d08 ce016bb05df949ebbafcc7c165359d7c ce1e819636744dc680fa5515f6475e87] [instance: 4e80964e-5bd1-4df4-a517-223c79d55517] networks retrieved for instance: |[<nova.db.sqlalchemy.models.Network object at 0x47f1d10>]| from (pid=1375) allocate_for_instance /usr/lib/python2.7/dist-packages/nova/network/manager.py:982

2.  Why is there a message sent to "network" on sonoma since I am running nova-network in single-host mode.  I don't have nova-network service running on the compute-node (hostname: sonoma):

2012-11-18 15:50:29 DEBUG nova.openstack.common.rpc.amqp [-] Making asynchronous call on network.sonoma ... from (pid=1375) multicall /usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/amqp.py:351
2012-11-18 15:50:29 DEBUG nova.openstack.common.rpc.amqp [-] MSG_ID is d73be9ea76b3412493d0752abb9d5a02 from (pid=1375) multicall /usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/amqp.py:354


3. Is it safe to assume the following RPC message timeout log entry (which seems to have a timeout value of 60 sec) related to above message sent to sonoma?

2012-11-18 15:51:29 ERROR nova.openstack.common.rpc.common [-] Timed out waiting for RPC response: timed out
2012-11-18 15:51:29 TRACE nova.openstack.common.rpc.common Traceback (most recent call last):
2012-11-18 15:51:29 TRACE nova.openstack.common.rpc.common   File "/usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/impl_kombu.py", line 513, in ensure
2012-11-18 15:51:29 TRACE nova.openstack.common.rpc.common     return method(*args, **kwargs)
2012-11-18 15:51:29 TRACE nova.openstack.common.rpc.common   File "/usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/impl_kombu.py", line 590, in _consume
2012-11-18 15:51:29 TRACE nova.openstack.common.rpc.common     return self.connection.drain_events(timeout=timeout)
2012-11-18 15:51:29 TRACE nova.openstack.common.rpc.common   File "/usr/lib/python2.7/dist-packages/kombu/connection.py", line 175, in drain_events
2012-11-18 15:51:29 TRACE nova.openstack.common.rpc.common     return self.transport.drain_events(self.connection, **kwargs)
…….

Can someone please help.

Regards,
Ahmed.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20121119/815767bc/attachment.html>