Infinidat Cinder driver generic volume migration feature is broken

Bug #1982405 reported by Alexander Deiter
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
In Progress
Low
Alexander Deiter

Bug Description

The Infinidat storage requires unique volume names for all pools within the same cluster.
But the Infinidat Cinder driver does not implement the standard function - update_migrated_volume.
These two circumstances make it impossible to perform a generic volume migration between two storage pools within the same cluster.

Steps to reproduce:
* Install an OpenStack environment
* Configure two Infinidat iSCSI or FC backends: backend1 and backend2
* Create a volume in the backend1
* Try to migrate the volume from backend1 to backend2

Expected results:
Success

Actual results:
The migration process fails with error:
ERROR: The volume cannot be deleted. Volume 'openstack-vol-1df0ce75-0356-4584-910b-7ab0f70e0175' has active mappings

Note:
The same issue can be reproduced in devstack environment with enabled multi-backend configuration and the Tempest test suite:
{0} tempest.scenario.test_volume_migrate_attached.TestVolumeMigrateRetypeAttached.test_volume_migrate_attached [97.003798s] ... FAILED
...
ERROR: The volume cannot be deleted. Volume 'openstack-vol-1df0ce75-0356-4584-910b-7ab0f70e0175' has active mappings

Root cause:
Function update_migrated_volume is not implemented in the Infinidat Cinder driver.

Changed in cinder:
status: New → In Progress
assignee: nobody → Alexander Deiter (adeiter)
description: updated
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cinder (master)

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/cinder/+/850320

Changed in cinder:
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers