Comment 4 for bug 2028338

Revision history for this message
Mohankumar (mohankumar-n) wrote :

you can see after multiple restart "L3 agent" stuck in unknown state.

stack@req-generic-73-3947-mn:~$ openstack network agent list --router r1 --long
+--------------------------------------+------------+------------------------+-------------------+-------+-------+------------------+----------+
| ID | Agent Type | Host | Availability Zone | Alive | State | Binary | HA State |
+--------------------------------------+------------+------------------------+-------------------+-------+-------+------------------+----------+
| 16e220ee-da1b-4dff-a7e9-2dc737ecf7eb | L3 agent | req-generic-73-3947-mn | nova | :-) | UP | neutron-l3-agent | unknown |
| 60864b8e-f52a-4f45-9dc0-70457658043e | L3 agent | req-generic-72-ea2a-mn | nova | :-) | UP | neutron-l3-agent | active |
+--------------------------------------+------------+------------------------+-------------------+-------+-------+------------------+----------+
stack@req-generic-73-3947-mn:~$

neutron-server.log: https://pastebin.ubuntu.com/p/TjcRc5ZMkB/

l3-agent.log: https://pastebin.ubuntu.com/p/KJN4TKqfjV/

In neutron server(q-svc logs) i couldn't find report_state loop, maybe Journalctl not collecting API logs