Matt Riedemann 58a140487c Block swap volume on volumes with >1 rw attachment ... 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. Conflicts: api-ref/source/os-volume-attachments.inc NOTE(mriedem): The conflict is due to not having change I5fc4d0ba3bb1c49dfaba2b2eed056441509cb9da in Queens. Also, the uuidsentinel has to be imported in the test_volumes module because change I9acc2e4d6c57ea0f45ba161116993d9f1a0e1e9f is not in Queens. Depends-On: https://review.openstack.org/573025/ Closes-Bug: #1775418 Change-Id: Icd7fcb87a09c35a13e4e14235feb30a289d22778 (cherry picked from commit 5a1d159d14) (cherry picked from commit 9b21d1067a) (cherry picked from commit c19d602f9b)		2019-05-30 17:29:53 -04:00
..
source	Block swap volume on volumes with >1 rw attachment	2019-05-30 17:29:53 -04:00