5a1d159d14
If we're swapping from a multiattach volume that has more than one read/write attachment, another server on the secondary attachment could be writing to the volume which is not getting copied into the volume to which we're swapping, so we could have data loss during the swap. This change does volume read/write attachment counting for the volume we're swapping from and if there is more than one read/write attachment on the volume, the swap volume operation fails with a 400 BadRequest error. Depends-On: https://review.openstack.org/573025/ Closes-Bug: #1775418 Change-Id: Icd7fcb87a09c35a13e4e14235feb30a289d22778
11 lines
472 B
YAML
11 lines
472 B
YAML
---
|
|
fixes:
|
|
- |
|
|
The `os-volume_attachments`_ update API, commonly referred to as the swap
|
|
volume API will now return a ``400`` (BadRequest) error when attempting to
|
|
swap from a multi attached volume with more than one active read/write
|
|
attachment resolving `bug #1775418`_.
|
|
|
|
.. _os-volume_attachments: https://developer.openstack.org/api-ref/compute/?expanded=update-a-volume-attachment-detail
|
|
.. _bug #1775418: https://launchpad.net/bugs/1775418
|