From e170225f3f4558bd13d302ac4379dd318cb12c93 Mon Sep 17 00:00:00 2001 From: Alexander Bashmakov Date: Wed, 14 Sep 2016 13:19:23 -0700 Subject: [PATCH] Update api-ref with 409 response to image update. With the change [1] that went into Newton to disallow image location updates except for 'queued' and 'active' states, this patch adds appropriate api-ref documentation. Related change [2] bumps the minor API version to 2.4. [1] https://review.openstack.org/324012 [2] https://review.openstack.org/350809 Change-Id: I593ad2d3c7402c4fb87a475c8d44060baed5ff69 Closes-Bug: 1621236 --- api-ref/source/v2/images-images-v2.inc | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/api-ref/source/v2/images-images-v2.inc b/api-ref/source/v2/images-images-v2.inc index 1b95f793be..f6dca95f28 100644 --- a/api-ref/source/v2/images-images-v2.inc +++ b/api-ref/source/v2/images-images-v2.inc @@ -476,13 +476,17 @@ fail with a 403 (Forbidden) response code: :ref:`Image Schema `. - An attempt to create or modify image properties for which you do not have - permission to do so. This depends upon how property protections are - configured in the OpenStack cloud in which you are making the call. Consult - your cloud's documentation for details. + permission to do so *(since Image API v2.2)*. This depends upon how property + protections are configured in the OpenStack cloud in which you are making the + call. Consult your cloud's documentation for details. + +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)*. Normal response codes: 200 -Error response codes: 400, 401, 403, 404, 413, 415 +Error response codes: 400, 401, 403, 404, 409, 413, 415 Request