summaryrefslogtreecommitdiff
path: root/releasenotes/notes/remove-multiattach-request-param-4444e02533f919da.yaml
diff options
context:
space:
mode:
Diffstat (limited to 'releasenotes/notes/remove-multiattach-request-param-4444e02533f919da.yaml')
-rw-r--r--releasenotes/notes/remove-multiattach-request-param-4444e02533f919da.yaml20
1 files changed, 20 insertions, 0 deletions
diff --git a/releasenotes/notes/remove-multiattach-request-param-4444e02533f919da.yaml b/releasenotes/notes/remove-multiattach-request-param-4444e02533f919da.yaml
new file mode 100644
index 000000000..0b11c4a48
--- /dev/null
+++ b/releasenotes/notes/remove-multiattach-request-param-4444e02533f919da.yaml
@@ -0,0 +1,20 @@
+---
+fixes:
+ - |
+ `Bug #2008259 <https://bugs.launchpad.net/cinder/+bug/2008259>`_:
+ Fixed the volume create functionality where non-admin users were
+ able to create multiattach volumes by providing the `multiattach`
+ parameter in the request body. Now we can only create multiattach
+ volumes using a multiattach volume type, which is also the
+ recommended way.
+other:
+ - |
+ Removed the ability to create multiattach volumes by specifying
+ `multiattach` parameter in the request body of a volume create
+ operation. This functionality is unsafe, can lead to data loss,
+ and has been deprecated since the Queens release.
+ The recommended method for creating a multiattach volume is to
+ use a volume type that supports multiattach. By default, volume
+ types can only be created by the operator. Users who have a need
+ for multiattach volumes should contact their operator if a suitable
+ volume type is not available.