Agent is not a L3 Agent or has been disabled

[[e-mail]]

[root@node-54-157 baoyongcheng]# quantum agent-list
+--------------------------------------+--------------------+-------------+-------+----------------+
| id | agent_type | host | alive | admin_state_up |
+--------------------------------------+--------------------+-------------+-------+----------------+
| 1a1ec969-9b17-4442-b5c8-cf5962fc8cf6 | DHCP agent | node-54-155 | xxx | True |
| 44401498-c9ad-4e9c-afd0-1bfffb6415f7 | Linux bridge agent | node-54-157 | :-) | True |
| 573462c4-7d76-4bf6-95f4-58bf3934e864 | L3 agent | node-54-157 | :-) | True |
| 58a2836e-12d2-42aa-a05c-4a79d41a776d | Linux bridge agent | node-54-155 | xxx | True |
| afa465a1-da2f-4654-9a8a-030fc044f7f8 | L3 agent | node-54-155 | xxx | True |
| b6f7f7ab-dab0-476f-96ae-644314775e53 | DHCP agent | node-54-157 | :-) | True |
+--------------------------------------+--------------------+-------------+-------+----------------+
[root@node-54-157 baoyongcheng]# quantum router-list
+--------------------------------------+---------+--------------------------------------------------------+
| id | name | external_gateway_info |
+--------------------------------------+---------+--------------------------------------------------------+
| ae001b60-ea59-4b93-b949-b763f9575365 | router1 | {"network_id": "4551f19b-48e2-4ac8-addc-6e97dd5f3f05"} |
+--------------------------------------+---------+--------------------------------------------------------+
[root@node-54-157 baoyongcheng]#
[root@node-54-157 baoyongcheng]# quantum l3-agent-list-hosting-router router1

[root@node-54-157 baoyongcheng]# quantum l3-agent-router-add 573462c4-7d76-4bf6-95f4-58bf3934e864 router1
Agent 573462c4-7d76-4bf6-95f4-58bf3934e864 is not a L3 Agent or has been disabled
[root@node-54-157 baoyongcheng]#

[dan wendlandt (danwent)]

hi yong, can you triage this bug? thanks.

[yong sheng gong (gongysh)]

Can u show me the configuration by:
quantum agent-show 573462c4-7d76-4bf6-95f4-58bf3934e864
and router information:
quantum router-show router1

[yong sheng gong (gongysh)]

If it is possible, can u contact me at openstack-dev channel?

[Brandon Lee (devmgr1)]

Hello,

I have this same problem. Also, my quantum-l3-agent stopped bringing up my router gateway IPs, and floating IPs. The agent starts up fine with no error logging, however, it's dead not doing anything.

+--------------------------------------+--------+--------------------------------------------------------+
| id | name | external_gateway_info |
+--------------------------------------+--------+--------------------------------------------------------+
| 4e7c832c-612e-4f03-839e-09ec667258dd | Public | {"network_id": "dbe6765b-582c-44fc-840a-9e23d35b19f7"} |
+--------------------------------------+--------+--------------------------------------------------------+

+--------------------------------------+--------------------+--------------------------------+-------+----------------+
| id | agent_type | host | alive | admin_state_up |
+--------------------------------------+--------------------+--------------------------------+-------+----------------+
| 02465d39-f50a-4087-957a-0948b38a3368 | Open vSwitch agent | compute-01.itcloudsuite.com | :-) | True |
| b2e968d5-ddc0-4dd3-8336-c0e21278ddb3 | Open vSwitch agent | controller-01.itcloudsuite.com | :-) | True |
| b85b1d88-0d57-425f-82a0-ddaac08287be | DHCP agent | controller-01.itcloudsuite.com | :-) | True |
| bf2cbb35-5460-4540-9429-41cc882c1176 | L3 agent | controller-01.itcloudsuite.com | :-) | True |
+--------------------------------------+--------------------+--------------------------------+-------+----------------+

[Pawel Koniszewski (pawel-koniszewski)]

I had the same problem today and I found why that thing happens. When you have namespaces turned off in quantum you must provide router id in l3_agent config file. When you change router to a brand new one and you don't change router id in l3_agent config file this will lead to that error. As long as there is provided wrong router id you will not be able to add router to l3_agent. This error message is kinda bad in that situation.