Greetings,
I've encountered what I believe to be a bug with New-VM -Template cmdlet and was wondering if anyone else could shed some light on this subject. I consistently get this network file copy error when I try to deploy a new vm from a template via powercli (error message below). I can do the exact same operation from the Vsphere web client and it will complete successfully. I have tested powercli version 6.3-6.5 and get the same results on each version. I am on a network with jumbo frames enable and have our hosts directly attached to storage via management NIC interface. Network latency is not an issue as both host and storage networks are dedicated. This is really just to be thorough because this exact same operation works when initiated from the web client. Please let me know if I can clarify anything and your input is appreciated. Thanks!
Error Message:
| New-VM : 3/21/2017 10:40:00 AM | New-VM | The operation for the entity "Template - Windows Server 2012r2" failed with the following message: "Could not complete network copy for file | |
| /vmfs/volumes/03195b0e-e6997962/Template - 2012r2/Template - 2012r2.vmdk" |
At line:1 char:1
+ New-VM -Name TestTemp -VMHost (Get-VMHost -Datastore esmc4_fucs1_f1c1 ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [New-VM], NetworkCopyFault
+ FullyQualifiedErrorId : Client20_TaskServiceImpl_CheckServerSideTaskUpdates_OperationFailed,VMware.VimAutomation.ViCore.Cmdlets.Commands.NewVM
This is the one liner I used to recreate the error message:
New-VM -Name TestTemp -VMHost (Get-VMHost -Datastore esmc4_fucs1_f1c1_incoming_01 | select -First 1) -Datastore "esmc4_fucs1_f1c1_incoming_01" -Template (Get-Template "Template - Windows Server 2012r2")
All the best,
Leander