Azure: return ARM errors when controller provisioning fails

[Sean Knox]

This might be a feature request.

STR:
- run `juju bootstrap azure/centralus`

EXPECTED:
- juju controller provisioned

ACTUAL:
- "ERROR failed to bootstrap model: instance provisioning failed (Failed)"

Looking into the Azure deployment logs, this is because the default VM size (Standard D1 v2) chosen for the Azure region isn't available to me:

{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.","details":[{"code":"Conflict","message":"{\r\n \"error\": {\r\n \"code\": \"SkuNotAvailable\",\r\n \"message\": \"The requested size for resource '/subscriptions/e766d9ee-d3d9-4b63-a912-8963dcfdf655/resourceGroups/juju-controller-model-16c34e2d-1167-4052-8811-b360bd99723e/providers/Microsoft.Compute/virtualMachines/machine-0' is currently not available in location 'centralus' zones '' for subscription 'e766d9ee-d3d9-4b63-a912-8963dcfdf655'. Please try another size or deploy to a different location or zones. See https://aka.ms/azureskunotavailable for details.\"\r\n }\r\n}"}]}

I had to jump quickly into the Azure Portal, find the juju deployment, and drill into the error to find this all before the entire juju resource group is automatically deleted. It would be help if juju reported this error back to the user so the user has guidance on how to fix.

[John A Meinel (jameinel)]

Just to clarify, is the goal to
a) Provide better error messaging when we are unable to provision an instance
b) Pick a different VM size
c) Pick a different region

How did you resolve the issue?

Does Azure have a way to know if an instance type is available (without actually trying to launch an instance)?

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.