I am building a PowerShell script to build out a SQL cluster comprised of VMs. I have a 2012 R2 Hyper-V cluster with shared FC. Everything is working fine on it. But I ran into a strange occurrence with the Add-VMHardDiskDrive cmdlet. It appears that it only works 'cleanly' on the node that owns the cluster name. Here is a screen shot.
The first time I issued the command, the cluster name was owned by a different node in the Hyper-V cluster. The second time I issued the command, the cluster name was owned by the same node on which I was executing the command. That's the only difference.
The other interesting thing about this is that even though I am receiving the warning and error, the VHDX file is properly added to the VM. So before I changed the ownership of the cluster group, I removed the VHDX file from the VM so that it would start at the same place on the VM.
I am running this from a Windows 8.1 VM that has all the latest patches and RSAT tools. The 2012 R2 cluster nodes are all up to date on published patches. The VMs are all 2012 R2 VMs.
Is this expected behavior?
.:|:.:|:. tim