After rbd based volume migrated (retyped), it will be
renamed to the original name unless name collision or
some errors happen. But the problem is this information
seems not reflect on connection info, especially this volume
is already in-use.
This patch mimics behavior of lvm driver by not renaming
in-used volume after migration(retype)
Close-Bug: #1866935
Change-Id: I4db0dc978d55d4704dd60e2eb8738b38ddefbbbd
(cherry picked from commit 662677280beedeb88a8161ddd3f08cfb95a9e5b6)
Reviewed: https:/ /review. opendev. org/715338 /git.openstack. org/cgit/ openstack/ cinder/ commit/ ?id=7c1118febca 2a0a0da9454372e 4ae03705d8007f
Committed: https:/
Submitter: Zuul
Branch: stable/train
commit 7c1118febca2a0a 0da9454372e4ae0 3705d8007f
Author: ushen <email address hidden>
Date: Mon Mar 9 19:34:24 2020 +0800
Do not rename rbd based volume after migration
After rbd based volume migrated (retyped), it will be
renamed to the original name unless name collision or
some errors happen. But the problem is this information
seems not reflect on connection info, especially this volume
is already in-use.
This patch mimics behavior of lvm driver by not renaming
in-used volume after migration(retype)
Close-Bug: #1866935
Change-Id: I4db0dc978d55d4 704dd60e2eb8738 b38ddefbbbd 88a8161ddd3f08c fb95a9e5b6)
(cherry picked from commit 662677280beedeb