From 8026e7f588786a9fc78d6c554725c30b3c4dd8fa Mon Sep 17 00:00:00 2001 From: Brian Rosmaita Date: Thu, 19 Oct 2017 18:45:42 -0400 Subject: [PATCH] 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 --- api-ref/source/v2/images-images-v2.inc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/api-ref/source/v2/images-images-v2.inc b/api-ref/source/v2/images-images-v2.inc index 604433d504..4efb99813a 100644 --- a/api-ref/source/v2/images-images-v2.inc +++ b/api-ref/source/v2/images-images-v2.inc @@ -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)*.