"No L3 agents can host the router..." traces for DVR

[Armando Migliaccio]

In a typical tempest run the Neutron Server's log is inundated of traces at WARN level that say:

 No L3 agents can host the router <bla>

An instance of this can be found here:

http://logs.openstack.org/91/114691/2/experimental/check-tempest-dsvm-neutron-dvr/93b2ff0/logs/screen-q-svc.txt.gz?level=WARNING

Although under some circumstances this may be acceptable, we would need to ensure that some of these do not mask scheduling errors, or more importantly, that they don't lead the admin to believe something is fundamentally wrong!

[Carl Baldwin (carl-baldwin)]

The discussion in the DVR meeting this morning has convinced me that we should probably raised the Importance of this bug because of its relation to FWaaS.

[Carl Baldwin (carl-baldwin)]

I think when we get a better handle on this bug then we may lower the Importance.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/116100

[OpenStack Infra (hudson-openstack)]

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

commit fb223cc1ebd3dc4d6f968346a2baa671acb6ffa2
Author: armando-migliaccio <email address hidden>
Date: Thu Aug 21 12:51:40 2014 -0700

    Do not log WARN messages about lack of L3 agents for DVR routers

    DVR routers are scheduled only when there is need to: for instance when
    there's an external gateway associated with it, or when there are
    interfaces attached to subnets on which VM's are actually being deployed.

    Therefore, do not log misleading messages that apply only to the
    centralized case.

    Closes-bug: 1358998

    Change-Id: Ica7f0d25fe576f05a9adf8eb8239704f09c0b0ac