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)
Reviewed: https:/ /review. opendev. org/711906 /git.openstack. org/cgit/ openstack/ cinder/ commit/ ?id=662677280be edeb88a8161ddd3 f08cfb95a9e5b6
Committed: https:/
Submitter: Zuul
Branch: master
commit 662677280beedeb 88a8161ddd3f08c fb95a9e5b6
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