sql-server-2014-alwayson-existing-vnet-and-ad stop during cluster configuration

sql-server-2014-alwayson-existing-vnet-and-ad https://github.com/Azure/azure-quickstart-templates/tree/master/sql-server-2014-alwayson-existing-vnet-and-ad

### Issue Details
The deploy works well until the cluster configuration phase with the following error:

VM has reported a failure when processing extension 'CreateCluster'. Error message: "DSC Configuration 'CreateFailoverCluster' completed with error(s). Following are the first few: Check the spelling of the cluster name. Otherwise, there might be a problem with your network. Make sure the cluster nodes are turned on and connected to the network or contact your network administrator. PowerShell DSC resource MicrosoftAzure_xCluster failed to execute Set-TargetResource functionality with error message: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: The computer 'xxxxx.xxxx.xxxx' is joined to a cluster.
Check the spelling of the cluster name. Otherwise, there might be a problem with your network. Make sure the cluster nodes are turned on and connected to the network or contact your network administrator.".

One sql server node is completely configured … the other one seem have the default configuration with the master and tempdb still in the default folders.

what's went wrong? How can solve the problem?

Thanks

Start with the sql-server-2014-alwayson-existing-vnet-and-ad template linked in the issue and inspect the CreateCluster extension and CreateFailoverCluster DSC error during cluster configuration. Reproduce the deployment and compare both SQL nodes after the failure; done means the cluster configures successfully and both nodes receive the intended SQL configuration.

Written by the indexing model from the issue text.