Unify exception thrown in l3-agent-scheduler fails
Since you can only attach a single l3 agent to a router, when you try
to add another l3 agent to a router that already have one, the l3
agent scheduler raises an exception.
This fix removes the discrimination by id: either it is the same agent
or another one, the router can not be hosted and the same exception is
raised.
Reviewed: https:/ /review. openstack. org/38599 github. com/openstack/ neutron/ commit/ 5db010a9a737356 e426e6f2e10c8fc afb36c533c
Committed: http://
Submitter: Jenkins
Branch: master
commit 5db010a9a737356 e426e6f2e10c8fc afb36c533c
Author: Jaume Devesa <email address hidden>
Date: Wed Jul 24 16:54:09 2013 +0200
Unify exception thrown in l3-agent-scheduler fails
Since you can only attach a single l3 agent to a router, when you try
to add another l3 agent to a router that already have one, the l3
agent scheduler raises an exception.
This fix removes the discrimination by id: either it is the same agent
or another one, the router can not be hosted and the same exception is
raised.
Change-Id: If832bbd4bf17e4 e0c4720172aded4 c9fffedc6fc
Fixes: bug #1154622