From fe69f679369057a7c381178f770bf68d0bc1cee0 Mon Sep 17 00:00:00 2001 From: Sean McGinnis Date: Thu, 26 Jul 2018 12:31:58 -0500 Subject: [PATCH] Add release note for force delete MV fix Change Ida04fc8a7a7af541547ea196a3cbb5a287714eea fixed an issue where we were checking the wrong microversion for support of the force delete functionality. This adds a release note to call out that previously this call might have been working when using a lower microversion but will no longer be allowed. Related-bug: #1783028 Change-Id: I660c934da053b576f817cdd349949873b0c30193 Signed-off-by: Sean McGinnis --- releasenotes/notes/force-delete-mv-a53924f09c475386.yaml | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 releasenotes/notes/force-delete-mv-a53924f09c475386.yaml diff --git a/releasenotes/notes/force-delete-mv-a53924f09c475386.yaml b/releasenotes/notes/force-delete-mv-a53924f09c475386.yaml new file mode 100644 index 00000000000..8eb2f9f39d8 --- /dev/null +++ b/releasenotes/notes/force-delete-mv-a53924f09c475386.yaml @@ -0,0 +1,9 @@ +--- +fixes: + - | + Volume "force delete" was introduced with the 3.23 API microversion, + however the check for in the service was incorrectly looking for + microversion 3.2. That check has now been fixed. It is possible that an API + call using a microversion below 3.23 would previously work for this call, + which will now fail. This closes + `bug #1783028 `_.