When host pool properties has "Distribute VMs across Availability Zones" setting enabled for VM Deployment, add host tasks can fail if the particular VM size SKU is unavailable for the availability zone that Nerdio tries to add the VM in. There doesn't seem to be logic in Nerdio that makes sure the particular SKU is available for the zone, prior to deployment. When auto-scale is trying to add a new host, it continually tries the same zone, and doesn't try another.
For example, Standard_E4s_v5 SKU is restricted in AZ2 for eastus2 region, only AZ1 and AZ3 are available.
But yet Nerdio tries deploying to it. Could logic be built-in to check for restrictions before adding a new VM?
Comments (3 comments)