Yes, I did try the default (i.e. Devstack plain) configuration with central routers and no complains were raised, as in I was able to set the gateway for the router to the second external network. Now, this might just mask a failure down the line because the L3 agent is not configured correctly, but that is probably a separate issue.
I had a look at the blog you linked, as well as [1] (thanks Miguel!), while I was triaging this bug.
The system is clearly not behaving correctly, perhaps due to a misconfiguration error. But why would the central case failure mode be different from the dvr one? A misconfiguration should be detected, and the right error should be returned. An internal server error is not very nice :)
I think there's some value in addressing the 500 error. Perhaps a 409 might be more appropriate, if we manage to detect what's actually going on?
Hi Mike,
Yes, I did try the default (i.e. Devstack plain) configuration with central routers and no complains were raised, as in I was able to set the gateway for the router to the second external network. Now, this might just mask a failure down the line because the L3 agent is not configured correctly, but that is probably a separate issue.
I had a look at the blog you linked, as well as [1] (thanks Miguel!), while I was triaging this bug.
The system is clearly not behaving correctly, perhaps due to a misconfiguration error. But why would the central case failure mode be different from the dvr one? A misconfiguration should be detected, and the right error should be returned. An internal server error is not very nice :)
I think there's some value in addressing the 500 error. Perhaps a 409 might be more appropriate, if we manage to detect what's actually going on?
[1] http:// www.ajo. es/post/ 86497974174/ using-multiple- external- networks- in-openstack- neutron