6cd3e190c6
Nova is trying to do a better job of mapping Neutron exceptions and change I4c087684ef77988e5f463d7f2f50fc2a04f37db0 is trying to map 409 to the proper nova exception. In looking at what raises a 409 exception in Neutron, the SubnetMismatchForPort exception seemed like a candidate for changing from Conflict (409) to BadRequest (400) to ease that mapping. Note that the only thing currently using this exception is the L3 router extension when removing a router interface and the 400 response code is already listed in the API docs as a possible response code: http://docs.openstack.org/api/openstack-network/2.0/content/router_remove_interface.html Also note that it's generally OK to change APIs for a more accurate response code: https://wiki.openstack.org/wiki/APIChangeGuidelines#Generally_Considered_OK Related-Bug: #1209446 Change-Id: I4507e1db69d738ec0f943f1b8b1209f269d5aebf
# -- Welcome!
You have come across a cloud computing network fabric controller. It has identified itself as "Neutron." It aims to tame your (cloud) networking!
# -- External Resources:
The homepage for Neutron is: http://launchpad.net/neutron . Use this site for asking for help, and filing bugs. Code is available on github at <http://github.com/openstack/neutron>.
The latest and most in-depth documentation on how to use Neutron is available at: <http://docs.openstack.org>. This includes:
Neutron Administrator Guide http://docs.openstack.org/trunk/openstack-network/admin/content/
Neutron API Reference: http://docs.openstack.org/api/openstack-network/2.0/content/
The start of some developer documentation is available at: http://wiki.openstack.org/NeutronDevelopment
For help using or hacking on Neutron, you can send mail to <mailto:openstack-dev@lists.openstack.org>.