Currently the new cinder attachment_create method allows volumes in
all status to be performed for single attachment. This may cause
problems if volume-attach operation is taken on volumes in creating
status.
In order to avoid these problems, we should only allow volumes
in 'in-use', 'reserved' status to check whether this attachment
creation is a override operation for a same instance.
Reviewed: https:/ /review. openstack. org/633177 /git.openstack. org/cgit/ openstack/ cinder/ commit/ ?id=6eba403ba02 0292806d0ec35ed c7964eaa8e8eaf
Committed: https:/
Submitter: Zuul
Branch: master
commit 6eba403ba020292 806d0ec35edc796 4eaa8e8eaf
Author: zhangyang <email address hidden>
Date: Fri Jan 25 18:11:17 2019 +0800
Create volume attachments status check.
Currently the new cinder attachment_create method allows volumes in
all status to be performed for single attachment. This may cause
problems if volume-attach operation is taken on volumes in creating
status.
In order to avoid these problems, we should only allow volumes
in 'in-use', 'reserved' status to check whether this attachment
creation is a override operation for a same instance.
Related-bug: #1694530 47a67a936c61e01 64fe278da99
Change-Id: Ie59f609d382901
Closes-Bug: #1813267