Description of problem: IHAC that would like to have the ability to migrate volumes between Cinder AZs Version-Release number of selected component (if applicable): RHOSP8 Additional info: Blueprint https://blueprints.launchpad.net/cinder/+spec/volume-migration-between-availability-zones
This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release.
This is now in stable/Queens [1] so it will be included in OSP13 on next rebase. [1]: https://review.openstack.org/#/c/550775/
I'll test then move to verified. For verification steps -> https://bugzilla.redhat.com/show_bug.cgi?id=1554784#c6
Verified on: openstack-cinder-12.0.1-0.20180418194613.c476898.el7ost.noarch Create a volume cinder create --display-name nfs2 --volume-type nfs 1 --availability-zone dc2 +--------------------------------+--------------------------------------+ | Property | Value | +--------------------------------+--------------------------------------+ | attachments | [] | | availability_zone | dc2 Retype/migrate to other backend LVM,Zone dc1 cinder retype 74f5d314-3e76-4d42-8e16-c05388344fee lvm --migration-policy on-demand Verify that volume successfully migrated to other availability zone -> dc1 cinder show 74f5d314-3e76-4d42-8e16-c05388344fee +--------------------------------+---------------------------------------+ | Property | Value | +--------------------------------+---------------------------------------+ | attached_servers | [] | | attachment_ids | [] | | availability_zone | dc1 | .. | | status | available Looking great, verified.
Hit a new bug, attached migration of vol, works but source volume remains. This doesn't happen with migration of a none attached volume. https://bugzilla.redhat.com/show_bug.cgi?id=1648931
Low usability bug. User isn't notified that migration (to other az) of a vol with snapshots failed. It fails due to snapshots this is the correct/expected result. But user isn't notified that no migration occurred. https://bugzilla.redhat.com/show_bug.cgi?id=1648941
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:0045