Ask Your Question
0

neutron.agent.metadata.agent [-] Failed reporting state!

asked 2015-02-16 11:09:28 -0600

Herr-Herner gravatar image

I get the following error in my OpenStack Juno installation (one-node) on Ubuntu 14.04:

2015-02-16 17:47:49.073 1517 INFO oslo.messaging._drivers.impl_rabbit [-] Connecting to AMQP server on os-controller.bui.materna.com:5672
2015-02-16 17:47:49.093 1517 INFO oslo.messaging._drivers.impl_rabbit [-] Connected to AMQP server on os-controller.bui.materna.com:5672
2015-02-16 17:47:49.104 1517 INFO oslo.messaging._drivers.impl_rabbit [-] Connecting to AMQP server on os-controller.bui.materna.com:5672
2015-02-16 17:47:49.122 1517 INFO oslo.messaging._drivers.impl_rabbit [-] Connected to AMQP server on os-controller.bui.materna.com:5672
2015-02-16 17:50:49.127 1517 ERROR neutron.agent.metadata.agent [-] Failed reporting state!
2015-02-16 17:50:49.127 1517 TRACE neutron.agent.metadata.agent Traceback (most recent call last):
2015-02-16 17:50:49.127 1517 TRACE neutron.agent.metadata.agent   File "/usr/lib/python2.7/dist-packages/neutron/agent/metadata/agent.py", line 351, in _report_state
2015-02-16 17:50:49.127 1517 TRACE neutron.agent.metadata.agent     use_call=self.agent_state.get('start_flag'))
2015-02-16 17:50:49.127 1517 TRACE neutron.agent.metadata.agent   File "/usr/lib/python2.7/dist-packages/neutron/agent/rpc.py", line 70, in report_state
2015-02-16 17:50:49.127 1517 TRACE neutron.agent.metadata.agent     return self.call(context, msg)
2015-02-16 17:50:49.127 1517 TRACE neutron.agent.metadata.agent   File "/usr/lib/python2.7/dist-packages/neutron/common/log.py", line 34, in wrapper
2015-02-16 17:50:49.127 1517 TRACE neutron.agent.metadata.agent     return method(*args, **kwargs)
2015-02-16 17:50:49.127 1517 TRACE neutron.agent.metadata.agent   File "/usr/lib/python2.7/dist-packages/neutron/common/rpc.py", line 161, in call
2015-02-16 17:50:49.127 1517 TRACE neutron.agent.metadata.agent     context, msg, rpc_method='call', **kwargs)
2015-02-16 17:50:49.127 1517 TRACE neutron.agent.metadata.agent   File "/usr/lib/python2.7/dist-packages/neutron/common/rpc.py", line 187, in __call_rpc_method
2015-02-16 17:50:49.127 1517 TRACE neutron.agent.metadata.agent     return func(context, msg['method'], **msg['args'])
2015-02-16 17:50:49.127 1517 TRACE neutron.agent.metadata.agent   File "/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/client.py", line 389, in call
2015-02-16 17:50:49.127 1517 TRACE neutron.agent.metadata.agent     return self.prepare().call(ctxt, method, **kwargs)
2015-02-16 17:50:49.127 1517 TRACE neutron.agent.metadata.agent   File "/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/client.py", line 152, in call
2015-02-16 17:50:49.127 1517 TRACE neutron.agent.metadata.agent     retry=self.retry)
2015-02-16 17:50:49.127 1517 TRACE neutron.agent.metadata.agent   File "/usr/lib/python2.7/dist-packages/oslo/messaging/transport.py", line 90, in _send
2015-02-16 17:50:49.127 1517 TRACE neutron.agent.metadata.agent     timeout=timeout, retry=retry)
2015-02-16 17:50:49.127 1517 TRACE neutron.agent.metadata.agent   File "/usr/lib/python2.7/dist-packages/oslo/messaging/_drivers/amqpdriver.py", line 408, in send
2015-02-16 17:50:49.127 1517 TRACE neutron.agent.metadata.agent     retry=retry)
2015-02-16 ...
(more)
edit retag flag offensive close merge delete

3 answers

Sort by ยป oldest newest most voted
1

answered 2015-02-16 23:07:15 -0600

Herr-Herner gravatar image

This is the output of neutron agent-list:

+--------------------------------------+--------------------+---------------+-------+----------------+---------------------------+
| id                                   | agent_type         | host          | alive | admin_state_up | binary                    |
+--------------------------------------+--------------------+---------------+-------+----------------+---------------------------+
| 8452fe3c-684d-44f5-af13-5fa8d62c86c4 | Open vSwitch agent | os-controller | :-)   | True           | neutron-openvswitch-agent |
| 906873eb-adaa-4658-b63a-73d928e57487 | DHCP agent         | os-controller | :-)   | True           | neutron-dhcp-agent        |
| a691e847-bfa3-4de0-92a0-9a15de2613de | Metadata agent     | os-controller | :-)   | True           | neutron-metadata-agent    |
| c8b8249b-2363-47d6-a9f8-3040a8fd8be3 | L3 agent           | os-controller | :-)   | True           | neutron-l3-agent          |
+--------------------------------------+--------------------+---------------+-------+----------------+---------------------------+
edit flag offensive delete link more

Comments

What maybe happening is the order in which services are started on your system. Since you are running an all in one system and after reboot if the meta-data comes up first and rabbit is not fully up then this can happen.

Since it works under normal conditions I think its safe to ignore!!!!

sfcloudman gravatar imagesfcloudman ( 2015-02-17 13:28:10 -0600 )edit
0

answered 2015-02-16 12:52:21 -0600

Looks like meta data agent can't connect to rabbitmq. If you look its says connecting 4 times and then gives up.

Neutron meta-data agent will use the rabbitmq settings in neutron.conf to connect to the message bus.

Is rabbitmq running on os-controller.bui.materna.com?

Did you provide the correct user name and password in to rabbit in neutron.conf?

edit flag offensive delete link more

Comments

I can see it in the RabbitMQ Management Plugin that neutron has a valid connection to the server. The credentials are correct and the server is up and running on the specified host. You can see it in the log file that the error occurs 3 minutes after a successful connect.

Herr-Herner gravatar imageHerr-Herner ( 2015-02-16 13:58:34 -0600 )edit

Can you run neutron agent-list and paste output .

sfcloudman gravatar imagesfcloudman ( 2015-02-16 15:00:55 -0600 )edit

How often do you see this error? Only after restart?

It would interesting if you can log in to the rabbitmq management web ui and see if there are message waiting for neutron meta-data agent.

sfcloudman gravatar imagesfcloudman ( 2015-02-16 23:15:14 -0600 )edit

It seems to be occur only after system restart. When I just restart the metadata-agent service, the error does not appear. I enabled the rabbitmq-tracing, but I am unfamiliar how to use it properly. The tracing must be activated directly after system restart.

Herr-Herner gravatar imageHerr-Herner ( 2015-02-17 01:59:32 -0600 )edit
0

answered 2017-02-24 06:23:52 -0600

Satyanarayana Patibandla gravatar image

Are you able to fix this issue. I am also facing same issue. In my case the same error is appeared after running few rally tasks.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2015-02-16 11:09:28 -0600

Seen: 3,071 times

Last updated: Feb 24 '17