router not found warning logs in the L3 agent

[Kevin Benton]

The L3 agent during a normal tempest run will be filled with warnings like the following:

2016-03-08 10:10:30.465 18962 WARNING neutron.agent.l3.agent [-] Info for router 3688a110-8cfe-41c6-84e3-bfd965238304 was not found. Performing router cleanup
2016-03-08 10:10:34.197 18962 WARNING neutron.agent.l3.agent [-] Info for router 3688a110-8cfe-41c6-84e3-bfd965238304 was not found. Performing router cleanup
2016-03-08 10:10:35.535 18962 WARNING neutron.agent.l3.agent [-] Info for router 3688a110-8cfe-41c6-84e3-bfd965238304 was not found. Performing router cleanup
2016-03-08 10:10:43.025 18962 WARNING neutron.agent.l3.agent [-] Info for router 3688a110-8cfe-41c6-84e3-bfd965238304 was not found. Performing router cleanup
2016-03-08 10:10:47.029 18962 WARNING neutron.agent.l3.agent [-] Info for router 3688a110-8cfe-41c6-84e3-bfd965238304 was not found. Performing router cleanup

This is completely normal as routers are deleted from the server during the data retrieval process of the L3 agent and should not be at the warning level.

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: master
Review: https://review.openstack.org/290281

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/290281
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=a33bc9957b80ab27b9f8a4610012026f766e5b0e
Submitter: Jenkins
Branch: master

commit a33bc9957b80ab27b9f8a4610012026f766e5b0e
Author: Kevin Benton <email address hidden>
Date: Tue Mar 8 19:23:13 2016 -0800

    Add logging statements to help debug L3 sync

    Add some debug logging statements to help determine why a
    requested router was not being returned to an L3 agent.

    Change-Id: I31eec599f11bb7e931984d436ef95e10bc9ffec2
    Related-Bug: #1554876

[Armando Migliaccio (armando-migliaccio)]

If this doesn't have a viable fix by the next day or so, it can't go in RC1