I think we've figured this out. In Victoria, storage assisted migration was added to Solidfire: https://review.opendev.org/c/openstack/cinder/+/746941. So prior to Victoria, cinder retype
was a host assisted migration using the generic cinder driver.
To workaround this, you can't use a volume type that has the "volume_backend_name" property set.
Essentially you can't refer to the backend at all it seems. If you instead create a volume type
with the "vendor_name='NetApp'" property, it looks like it reverts to a host assisted migration and the cinder retype works.
I think we've figured this out. In Victoria, storage assisted migration was added to Solidfire: /review. opendev. org/c/openstack /cinder/ +/746941. So prior to Victoria, cinder retype
https:/
was a host assisted migration using the generic cinder driver.
After Victoria, it's now handled by the Solidfire driver as a storage assisted migration. And /github. com/openstack/ cinder/ commit/ b1d6210d454c05a eca2fbe944c6b6e 82c508372f# diff-a62544f589 ca8b9ea1f17078e c5fb30aa687f3dd e2b8125b1928cf2 44832f6b9R2425.
it looks like cinder retype (when run as a storage assisted migration) on works for volume migrations
between two solidfire clusters: https:/
To workaround this, you can't use a volume type that has the "volume_ backend_ name" property set. name='NetApp' " property, it looks like it reverts to a host assisted migration and the cinder retype works.
Essentially you can't refer to the backend at all it seems. If you instead create a volume type
with the "vendor_