When attempting to add a node to an existing Hyper-V cluster, the cluster validation test fails on the 'Validate Hyper-V Virtual Machine Storage Configuration' test. All permissions on Hyper-V shares where VM configs and VHDXs are housed, are correct with each host object having 'Full Control' on the share. If the node is forced into the cluster, essentially overriding/skipping the test, both nodes operate as normal, with failover also working without issue.
What is wrong with the validation tool? Why is it failing to see the shared storage for one host?
After moving one VM to another host, we ran the tests again. The tests failed again, with each host still failing to see the shared storage, despite the VMs running without issue on either host! What gives?
The validation test is also picking up on a difference in the number of updates between both hosts. Both hosts have reported recently into WSUS, and the number of installed updates is identical. Working through the list of missing updates, we have verified if it really is the case by runninga WSUS report for that host. The host is NOT missing the updates reported by the validation tool, and this is also confirmed by the presence of the update on the host when viewing the 'Installed Updates' list.
Seems the validation wizard has it all wrong! Has anyone seen this before? Which machine is it contacting when running reports? It sure as hell isn't the host we're running it against!