301-sql-alwayson-md-ilb-zones - sqlConfig timeout

[wesback]

301-sql-alwayson-md-ilb-zones (https://github.com/Azure/azure-quickstart-templates/tree/master/301-sql-alwayson-md-ilb-zones)

Issue Details

Deployment times out on sqlConfig step Looking at the logs it seems to be at the point where nodes get added to the cluster. VERBOSE: [2018-09-03 11:26:11Z] [VERBOSE] [xxxxxxxxxxxx]:
[[xCluster]FailoverCluster] at MS.Internal.ServerClusters.NativeMethods.OpenCluster(String clusterName, ClusterAccessRights desiredAccess, ClusterAccessRights& grantedAccess) at MS.Internal.ServerClusters.Cluster.Open(String clusterName, ClusterAccessRights desiredAccess) at Microsoft.FailoverClusters.PowerShell.ClusterBridge.Open(String name, ClusterAccessRights desiredAccess) at Microsoft.FailoverClusters.PowerShell.ClusterPipeCmdlet.get_Clus() at Microsoft.FailoverClusters.PowerShell.GetNodeCommand.WrappedProcessRecord() at Microsoft.FailoverClusters.PowerShell.FCCmdlet.ProcessRecord() VERBOSE: [2018-09-03 11:26:41Z] [VERBOSE] [xxxxxxxxxxxx]:
[[xCluster]FailoverCluster] Finding nodes in cluster 'xxxxxxxxxxxxclu'

[wesback]

It was a DNS issue

[kjhosein]

Adding some more color to this issue for anyone searching for the fantastic error message: "Microsoft.FailoverClusters.PowerShell.ClusterBridge.Open(String name, ClusterAccessRights desiredAccess)", where you get 4 Google search results, 2 of which are just build reports!

I was puzzled by @wesback's comment, but it eventually got me heading down the right path. In my case, I had a semi-built cluster where the CNO had already been created in Active Dir, as well as a DNS entry. But then there was a failure (race condition where I had messed something up) and when I tried kicking off the build again, I got this error.

The answer (for me) was to blow away the cluster, the AD object for the CNO, and the DNS entry, then retry the process. Depending on your code, you may only need to delete the DNS entry.

-- † NOTE: although I'm commenting here, I was not using this Azure quickstart template, but I am using the xFailOverCluster DSC module.