api-ref: add notes about POST/DELETE errors for os-tenant-networks

After microversion 2.35 all of the os-tenant-networks methods will
return a 404 response. However, before that, if using neutron:

- POST will return a 503 error because the NotImplementedError is
  caught and translated to the 503.
- DELETE will return a 500 error because the NotImplementedError
  is NOT caught so results in a 500.

The API reference only noted that the API is deprecated since the
2.36 microversion but doesn't note that POST and DELETE are not
implemented, so this adds those details for unsuspecting victims.

Change-Id: I7f256a4c1a6e4247698fcb5ee7c56128c517e29b
Closes-Bug: #1652252
This commit is contained in:
Matt Riedemann 2016-12-29 16:44:22 -05:00
parent a74d3ae4e8
commit f9bfb72a1c
1 changed files with 10 additions and 0 deletions

View File

@ -45,6 +45,11 @@ Create Project Network
.. rest_method:: POST /os-tenant-networks
.. note::
This API is only implemented for the nova-network service and will result
in a 503 error response if the cloud is using the Neutron networking
service. Use the Neutron ``networks`` API to create a new network.
Creates a project network.
Policy defaults enable only users with the administrative role to
@ -104,6 +109,11 @@ Delete Project Network
.. rest_method:: DELETE /os-tenant-networks/{network_id}
.. note::
This API is only implemented for the nova-network service and will result
in a 500 error response if the cloud is using the Neutron networking
service. Use the Neutron ``networks`` API to delete an existing network.
Deletes a project network.
Policy defaults enable only users with the administrative role or