+++ This bug was initially created as a clone of Bug #1845631 +++

+++ This bug was initially created as a clone of Bug #1835870 +++

Description of problem:

The volume migration from Netapp to 3par shows success on the terminal/CLI output but below error can be seen in cinder-volume logs while renaming the initial copy of the volume in 3par cinder backend:

~~~~~~~~
2020-05-14 14:51:38.213 66 ERROR cinder.volume.drivers.hpe.hpe_3par_common [req-edcc2612-9432-4522-bc2e-f4f5fbefbf18 d93d94d0eba0474294590ba2d7557b8e 869bf59fe6e743ed94b96702a3a67bcd - default default] Changing the volume name from osv-5eze4pUtS36GJKKAV6XYLA to osv-4eZB--17SPqSA88PLwka4g failed because Not found (HTTP 404) 23 - volume does not exist: HTTPNotFound: Not found (HTTP 404) 23 - volume does not exist
~~~~~~~~

which further affects any operations on the retyped volume like launching an instance using this volume.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Install an OSP 13 environment with 2 cinder FC backends i.e Netapp and 3par
2. Create a bootable volume in Netapp cinder backend
3. Migrate the volume from Netapp to 3par cinder backend using "cinder retype" command
4. Launch an instance from the volume once it is migrated to 3par cinder backend and it should fail with below error:

BuildAbortException: Build of instance 2447bab0-62dd-4b59-a9cd-8662a4488902 aborted: Unable to update attachment.(Bad or unexpected response from the storage volume backend API: Driver initialize connection failed (error: Not found (HTTP 404) 23 - volume does not exist).). (HTTP 500) (Request-ID: req-6af8c8be-9f73-4077-856f-9d9f27d6b45c)

Actual results:
Openstack server create operation fails with a volume migrated to 3par cinder backend from Netapp cinder backend.


Expected results:
Openstack operations should behave the same on a migrated volume as it works for a non-migrated volume.