After upgrading to WFA 4.1.0.0.1RC1, we receive the following when executing the "Clone Volume" command.
10:37:44.436 INFO [Clone volume] ### Command 'Clone volume' in 'POWER_SHELL' ###
10:37:46.608 INFO [Clone volume] Get-WfaCredentials -Host clus1
10:37:46.639 INFO [Clone volume] Credentials successfully provided for 'clus1'
10:37:46.671 INFO [Clone volume] Connect-Controller -Type CLUSTER -Name clus1 -Credential System.Management.Automation.PSCredential -Vserver
10:37:46.749 INFO [Clone volume] Connect-NcController (with credentials) -Name clus1 -Timeout 60000 -ErrorAction Stop
10:37:49.030 INFO [Clone volume] Connected to cluster node
10:37:49.921 INFO [Clone volume] Create a clone for Volume 'vol1' , named 'vol2' on Storage Virtual Machine 'clus1v01'
10:37:49.968 ERROR [Clone volume]
| This cmdlet must be directed to a data vserver. You are currently connected |
| to the cluster admin vserver. See the Toolkit web docs (Show-NcHelp) or online |
| help (Get-Help Connect-NcController -Examples) to learn more about directing |
| Toolkit cmdlets to a cluster or data vserver as required by Data ONTAP. |
10:37:50.077 ERROR [Clone volume] Command failed for Workflow 'Workflow' with error :
| This cmdlet must be directed to a data vserver. You are currently connected |
| to the cluster admin vserver. See the Toolkit web docs (Show-NcHelp) or online |
| help (Get-Help Connect-NcController -Examples) to learn more about directing |
| Toolkit cmdlets to a cluster or data vserver as required by Data ONTAP. |
10:37:50.077 INFO [Clone volume] ***** Workflow Execution Failed *****
In the above output, the -Vserver value is missing from the following:
10:37:46.671 INFO [Clone volume] Connect-Controller -Type CLUSTER -Name clus1 -Credential System.Management.Automation.PSCredential -Vserver
To workaround, I modified the following code line in the "Clone Volume" command as follows:
Before:
Connect-WfaCluster -Node $Cluster
After:
Connect-WfaCluster -Node $Cluster -Vserver $VserverName
Of course, this is not ideal, because it's still broken if you use $ParentVserver