NetApp NFS Storage Migration between backends is Failing

Description
===========
Migrating a Cinder volume from a NetApp NFS backend to another (different SVM, but same Cluster) is failing in case those backends have same FlexVol name.

The NFS NetApp driver, the pool is the FlexVol volume in ONTAP, while a Cinder backend is one of the SVMs. So, we can have two backends each one a different SVM and defining the pools with FlexVol volumes with same name. In this case, migrating a Cinder volume from one to another will fail using the storage assisted migration.

Steps to reproduce
==================

- Configuring two backends with different SVMs: BACKEND1 and BACKEND2
- Configuring the pools of those backends with volumes with same name (REPEATED_VOL)

Running a get pools command in Cinder would have 2 pools:
host@BACKEND1#10.10.10.1:/REPEATED_VOL
host@BACKEND2#10.10.10.2:/REPEATED_VOL

1) Create a volume:
cinder create 1 --volume-type netapp --name v1

2) Migrate the volume to the other backend:
cinder migrate v1 host@BACKEND2#10.10.10.2:/REPEATED_VOL

Expected result
===============

It should migrate the volume to the other backend.

Actual result
=============

It fails during the migration process. The log error message:

https://paste.opendev.org/show/btKB7T3lGj91Uz7hPrOz/