openstack
/
glance
Code Issues Proposed changes

Update api-ref about 403 for image location changes 

Add deleting the only location or attempting to set the locations
to an empty list as another reason why a user might get a 403
response to a PATCH call.

Change-Id: I2edb072ded11d1b710af0309f0372d1b16042a54
Closes-bug: #1542724
This commit is contained in:
Brian Rosmaita 2017-10-19 18:45:42 -04:00
parent 4731910f94
commit 8026e7f588
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
api-ref/source/v2/images-images-v2.inc
View File

@ -531,6 +531,9 @@ fail with a 403 (Forbidden) response code:
protections are configured in the OpenStack cloud in which you are making the
call. Consult your cloud's documentation for details.
- An attempt to delete the only image location, or to replace the image
locations with an empty list *(since Image API v2.4)*.
Attempting to add a location path to an image that is not in ``queued`` or
``active`` state will result in a 409 (Conflict) response code
*(since Image API v2.4)*.