Ask Your Question

Queens: openstack network agent list is missing nova metadata agent

asked 2018-09-20 14:29:30 -0500

nag gravatar image

updated 2018-09-20 23:57:58 -0500

image description

    vim  /var//log/neutron/linuxbridge-agent.log 

    ERROR neutron.plugins.ml2.drivers.agent._common_agent [-] Failed reporting state!: MessagingTimeout: Timed out waiting for a reply to message ID f1f5e05ffedc4350ac307a676dd3f6aa

    **compute node**

    **root@compute01 ~]# systemctl status neutron-linuxbridge-agent.service**

    ● neutron-linuxbridge-agent.service - OpenStack Neutron Linux Bridge Agent
       Loaded: loaded (/usr/lib/systemd/system/neutron-linuxbridge-agent.service; enabled; vendor preset: disabled)
       Active: **failed (Result: start-limit**) since Thu 2018-09-20 18:31:11 EDT; 14min ago

      Process: 38407 ExecStart=/usr/bin/neutron-linuxbridge-agent --config-file /usr/share/neutron/neutron-dist.conf --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/linuxbridge_agent.ini --config-dir /etc/neutron/conf.d/common --config-dir /etc/neutron/conf.d/neutron-linuxbridge-agent --log-file /var/log/neutron/linuxbridge-agent.log (code=exited, status=1/FAILURE)

      Process: 38400 ExecStartPre=/usr/bin/ (code=exited, status=0/SUCCESS)
     Main PID: 38407 (code=exited, status=1/FAILURE)

    Sep 20 18:31:11 compute01 systemd[1]: **Unit neutron-linuxbridge-agent.service entered failed state.**
    Sep 20 18:31:11 compute01 systemd[1]**: neutron-linuxbridge-agent.service failed.**
    Sep 20 18:31:11 compute01 systemd[1]: neutron-linuxbridge-agent.service holdoff time over, scheduling restart.
    Sep 20 18:31:11 compute01 systemd[1]: start request repeated too quickly for neutron-linuxbridge-agent.service
    Sep 20 18:31:11 compute01 systemd[1]: **Failed to start OpenStack Neutron Linux Bridge Agent.**
    Sep 20 18:31:11 compute01 systemd[1]: **Unit neutron-linuxbridge-agent.service entered failed state.**
    Sep 20 18:31:11 compute01 systemd[1]: **neutron-linuxbridge-agent.service failed.**
    [root@compute01 ~]#

[root@controller opt]# openstack network agent list
| ID                                   | Agent Type         | Host       | Availability Zone | Alive | State | Binary                    |
| 109 | Linux bridge agent | compute02  | None        | :-)   | UP    | neutron-linuxbridge-agent |
| 188 | DHCP agent         | controller | nova              | :-)   | UP    | neutron-dhcp-agent        |
| 2f4 | Linux bridge agent | controller | None            | :-)   | UP    | neutron-linuxbridge-agent |
| 4ff | L3 agent           | controller | nova                 | :-)   | UP    | neutron-l3-agent          |
| ca0| Metadata agent     | controller | None            | :-)   | UP    | neutron-metadata-agent    |
[root@controller opt]# 

I added new compute02 node it's fine, from the new node copied nova.conf and neutron.conf file(changed management ip) but no luck
edit retag flag offensive close merge delete

1 answer

Sort by » oldest newest most voted

answered 2018-09-20 16:30:06 -0500

updated 2018-09-20 17:34:10 -0500

Nova doesn’t have a metadata agent, and if it did, it would be listed by Nova, not Neutron. However, Neutron has a metadata agent, and it is listed.

The Linuxbridge agent’s message timeouts on the compute node could be an effect of unsynchronized clocks. Ensure that controller and compute node(s) have exactly the same time.

Your logs are almost unreadable. Please format them as code. They also seem to be mixed up a little: The first series of timestamps is around 13:20, then a few seemingly unrelated logs from 1am, then again around 15:50.

edit flag offensive delete link more


Now compute node is synced with Controller. Still Nova Metadata agent is missing

nag gravatar imagenag ( 2018-09-20 17:49:22 -0500 )edit

The Nova metadata agent is missing in all OpenStack clouds, since Nova doesn't have a metadata agent.

Is your Linuxbridge agent now running on the compute node?

By "format as code" I meant this button:

image description

Bernd Bausch gravatar imageBernd Bausch ( 2018-09-20 22:45:01 -0500 )edit

I understand that compute02 works, and although you copied its configuration to compute01, the linuxbridge-agent on compute01 has the same problem as before.

I can't tell what's wrong. Have you restarted the agent? Do the two compute nodes have the same software installed? Network/Firewall setting?

Bernd Bausch gravatar imageBernd Bausch ( 2018-09-21 00:25:29 -0500 )edit

Also double-check the time. And perhaps there are other useful messages in the log when the agent starts.

Bernd Bausch gravatar imageBernd Bausch ( 2018-09-21 00:26:30 -0500 )edit

Thanks allot Bernd, i am not sure what's wrong. I have un-installed the compute and network service pakages and re-installed again, restarted all the services. Now it's working. I appreciate your help.

nag gravatar imagenag ( 2018-09-21 16:39:26 -0500 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2018-09-20 14:29:30 -0500

Seen: 797 times

Last updated: Sep 20 '18