Activity log for bug #1753290

Date Who What changed Old value New value Message
2018-03-04 18:01:14 Sean Knox bug added bug
2018-03-04 18:05:37 Sean Knox description 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 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. 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.
2018-03-14 10:27:27 John A Meinel juju: importance Undecided High
2018-03-14 10:27:27 John A Meinel juju: status New Triaged
2022-11-03 16:41:01 Canonical Juju QA Bot juju: importance High Low
2022-11-03 16:41:02 Canonical Juju QA Bot tags feature expirebugs-bot feature