Hopefully someone can help with this mystery
I have a 3 Node 2008R2 Hyper-v cluster connected to NetApp iscsi storage
Cannot live migrate or quick migrate if the underlying cluster shared volume is not owned by the node to which the vm is being migrated. Even after moving storage live migration may fail or the running vm may shut down. The only elegant way to achieve any form of migration is to shut down the vms running on any CSV and migrate that volume and move all the machines to the node now owning the CSV.
Following Event ids are logged:
Event Id 1069 from source FailoverClustering “Cluster resource 'Virtual Machine Configuration <VMName> in clustered service or application <VMName> failed.”
Event Id 1205 from source FailoverCLustering “The Cluster service failed to bring clustered service or application <VMName> completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.”
Event id 4096 from source Hyper-V-Config “The Virtual Machines configuration 3989B536-28A2-48EB-982E-7B92E0235D54 at 'C:\ClusterStorage\Volume9\<VMName>' is no longer accessible: Logon failure: unknown user name or bad password. (0x8007052E)”
Event Id 16300 from source Hyper-v-VMMS “Cannot load a virtual machine configuration: Logon failure: unknown user name or bad password. (0x8007052E) (Virtual machine ID 3989B536-28A2-48EB-982E-7B92E0235D54)”
Event Id 20100 from source Hyper-V-VMMS :The Virtual Machine Management Service failed to register the configuration for the virtual machine '3989B536-28A2-48EB-982E-7B92E0235D54' at 'C:\ClusterStorage\Volume9\<VMName>': Logon failure: unknown user name or bad password. (0x8007052E)”
Event id 21102 from source Hyper-v-High-Availability “Virtual Machine Configuration <VMName> failed to register the virtual machine with the virtual machine management service.”
Event id 21502 from source Hyper-v-High-Availability “Virtual Machine Configuration <VMName> failed to register the virtual machine with the virtual machine management service.”
Cluster configuration passes validity with few minor warnings that I have always had previously and everything worked fine.
If I try to browse cluster storage volumes at c:\clusterstorage\Volumex from a non-owning node I get:
C:\ClusterStorage\Volumex is not accessible.
Logon failure: unknown user name or bad password.
This behavior to the best of my knowledge has started after the latest set of patches released by MS on March 2015. There are no authentication protocols between the SAN and the Hyper-v cluster nodes. I do not want to rollback all the patches and then do a trial and error process if I can help it.
Googling / Binging for these set of combined symptons has led to absolutely nothing useful. Am willing to post a sanitised cluster log if necessary.
Thanks