When users update router hosted by l3_agent, neutron server casts unnecessary notification even if the l3_agent is set admin_state_up False .
$ neutron --os-username admin --os-password openstack l3-agent-list-hosting-router router1
+--------------------------------------+--------------------------+----------------+-------+
| id | host | admin_state_up | alive |
+--------------------------------------+--------------------------+----------------+-------+
| 25991a37-5f6c-41bb-a80f-c2e41cdc3a0f | vagrant-ubuntu-trusty-64 | False | :-) |
+--------------------------------------+--------------------------+----------------+-------+
$ neutron router-interface-add router1 subnet
Added interface d0985c72-08d0-4f87-b825-9dba1d257823 to router router1.
l3_agent log:
2015-01-14 15:18:46.937 DEBUG neutron.agent.l3.agent [req-1ecc6f52-49c7-4e3a-aa98-a949aefc65cd demo e7f0cdeb333c4b21a9acdacbe9b50a86] Got routers updated notification :[u'154aa9bd-4950-4ccc-a26f-c9278f9da0c4'] from (pid=11845) routers_updated /opt/stack/neutron/neutron/agent/l3/agent.py:977
2015-01-14 15:18:46.937 DEBUG neutron.agent.l3.agent [req-1ecc6f52-49c7-4e3a-aa98-a949aefc65cd demo e7f0cdeb333c4b21a9acdacbe9b50a86] Starting router update for 154aa9bd-4950-4ccc-a26f-c9278f9da0c4 from (pid=11845) _process_router_update /opt/stack/neutron/neutron/agent/l3/agent.py:1051
2015-01-14 15:18:46.953 WARNING neutron.agent.l3.agent [req-1ecc6f52-49c7-4e3a-aa98-a949aefc65cd demo e7f0cdeb333c4b21a9acdacbe9b50a86] Info for router 154aa9bd-4950-4ccc-a26f-c9278f9da0c4 were not found. Skipping router removal
The meaning of admin_state_up is under discussion now. See this thread.[1]
If we go the way of admin_state_up only indicating scheduling candidacy, then this is behaving just as we would want it.
1. http:// lists.openstack .org/pipermail/ openstack- dev/2015- January/ 053782. html