centralized router is scheduled to dvr configured agent

[Mike Smith]

The recent changes to the l3-scheduler should support the new agent_modes for l3-agent. When the agent_mode=dvr only dvr routers should be scheduled to that agent. But currently centralized routers are being scheduled there

[Mike Smith (michael-smith6)]

I have a fix for this - I will post a patch for review soon.

[Armando Migliaccio (armando-migliaccio)]

I observed this error here:

http://logs.openstack.org/77/108177/10/experimental/check-tempest-dsvm-neutron-dvr/9e67d95/logs/screen-q-svc.txt.gz?level=TRACE#_2014-07-31_15_05_48_864

It looks like the scheduling process fails because of a duplicate entry to the agent/router binding table. This might be an effect of fix:

https://review.openstack.org/#/c/73234/

Not sure if the proposed fix you mention here also addresses the issue I have seen. I'll post more details when I find them

[Armando Migliaccio (armando-migliaccio)]

The failure reported in comment #2 looks like it's different. Reporting in a separate bug.

[OpenStack Infra (hudson-openstack)]

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

commit b844085d21622c11fd0735ae6944dd14cae5c5c3
Author: Michael Smith <email address hidden>
Date: Wed Jul 30 23:17:47 2014 -0700

    centralized router is incorrectly scheduled

    When agent_mode=dvr only distributed routers should be
    scheduled to that agent. This change fixes this problem
    by not allowing centralized routers to be scheduled
    to an agent configured with agent_mode=dvr

    Closes-bug: 1350667
    Change-Id: I34e118535094520f2cee853f39d582a625acde20