Activity log for bug #1982405

Date Who What changed Old value New value Message
2022-07-20 17:08:28 Alexander Deiter bug added bug
2022-07-20 17:08:36 Alexander Deiter cinder: status New In Progress
2022-07-20 17:08:40 Alexander Deiter cinder: assignee Alexander Deiter (adeiter)
2022-07-21 07:42:29 Alexander Deiter 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 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. 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.
2022-07-26 20:05:52 Sofia Enriquez cinder: importance Undecided Low
2022-11-30 15:23:18 Sofia Enriquez cinder: importance Low High
2022-12-16 23:28:52 OpenStack Infra cinder: status In Progress Fix Released
2023-06-15 11:49:18 OpenStack Infra tags drivers infinidat drivers in-stable-zed infinidat