ACS cluster is not ready to use after deployment template reports success

[sanar-microsoft]

Is this a BUG REPORT or FEATURE REQUEST? (choose one):

BUG report.

Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm)

Kubernetes.

What happened:

ACS cluster is not ready after getting created. Not able to make an SSH connection and run kubectl commands for a couple of minutes.

What you expected to happen:

ACS cluster should be ready to use when the creation template returns success. The creation should return success only after the cluster has Kubernetes binaries and other dependencies installed.

How to reproduce it (as minimally and precisely as possible):

1. Create a new ACS cluster (I used the Azure SDK, ComputeClient.ContainerServices.CreateOrUpdateAsync)
2. As soon as the cluster is created, try to create an SSH connection to the master. Connection will be aborted by the server.
3. The SSH connection will eventually succeed, run any kubectl command on the cluster. An error: kubectl: command not found is returned.
4. Kubectl commands will be available to use after some time.

Anything else we need to know:

On examining the /var/log/auth.log file on the cluster for SSH connection failures, this is the logged statement: fatal: Access denied for user azureuser by PAM account configuration [preauth].