From 58bf19d497853122e6183f54d6d1b1982fc5fd52 Mon Sep 17 00:00:00 2001 From: Brian Rosmaita Date: Tue, 31 Jan 2017 09:16:58 -0500 Subject: [PATCH] Correct 2.5 minor version bump release note Current release note says adding a member to a private image will result in a 409, but it actually results in a 403. Changing the text to say the more neutral "4xx response" without specifying a return code, because there are several errors that could happen here, for example, 401, 404, 403. Interested parties will know to look in the api-ref, where the error codes can be listed with more context than is appropriate for a release note. Change-Id: If513e5a0441b2c110c9339544a47ad33d77afaaf --- .../notes/api-minor-version-bump-bbd69dc457fc731c.yaml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/releasenotes/notes/api-minor-version-bump-bbd69dc457fc731c.yaml b/releasenotes/notes/api-minor-version-bump-bbd69dc457fc731c.yaml index b4f7735947..9d0f075c52 100644 --- a/releasenotes/notes/api-minor-version-bump-bbd69dc457fc731c.yaml +++ b/releasenotes/notes/api-minor-version-bump-bbd69dc457fc731c.yaml @@ -15,4 +15,6 @@ upgrade: In this release, an image must have a visibility of ``shared`` in order to accept member operations. Attempting to add a member to an image with a visibility of ``private`` will result - in a 409 (Conflict) response. + in a `4xx response`_ containing an informative message. + + .. _`4xx response`: https://developer.openstack.org/api-ref/image/v2/?expanded=create-image-member-detail#create-image-member