VASA Provider: SVM name breaks SvMotion when using vVols
Applies to
- VASA Provider (VP) 9.11
- VMware vCenter
Issue
When using vVols datastores within VMware environment, an issue is seen when performing a Storage only vMotion (SvMotion) from a non-vVol datastore to a vVol datastore.
The following error will be seen in vCenter's Event Log:
Failed to relocate SiteA-vm01 from esx1.demo.netapp.com , iscsi2 in Site A - demo.netapp.com to esx1.demo.netapp.com , test_vvol in Site A - demo.netapp.com
Error caused by file /vmfs/volumes/63d84e3e-f43f508d-bf17-005056b7c87e/SiteA-vm01/SiteA-vm01.vmdk
An error similar to the following is seen in the vvolvp.log:
2023-01-20T15:53:52.745Z error hostd[2100705] [Originator@6876 sub=Libs opID=ld3ly9qx-8838-auto-6tj-h5:70002973-23-01-3b2e user=vpxuser:IPADS\DeLeonAA-pa] 2100705:VVOLLIB : VVolLibVasaTaskHandler:1939: VASA task (arrayID:'NetApp.clustered.Data.ONTAP.VP:f84bfe38206f41288f1c00000098aa3d', task:'10021001') has completed with FAILURE: (STORAGE_FAULT, AbstractController: id: 26666451-8b80-11ed-b0b3-d039ea054c13name: svm_fc.vvol ip address: 192.168.0.137 failed to create QoS policy named VASA_Default_QoS_INF_svm_fc_vvol. duplicate entry (errno=13130)) The VVol target encountered a vendor specific error
2023-01-20T15:53:52.745Z error hostd[2100705] [Originator@6876 sub=Libs opID=ld3ly9qx-8838-auto-6tj-h5:70002973-23-01-3b2e user=vpxuser:IPADS\DeLeonAA-pa] 2100705:VVOLLIB : VVolLibExecuteVasaTask:3501: Task of type 0x5ca1ab1e failed (retval: The VVol target encountered a vendor specific error)