Template-based creates should unwrap deployment errors.

[colemickens]

$ az vm create ...

The template deployment 'vm_deploy_RtLRcxVrhUTZ2eRr616EQweSuEujmT0c' is not valid according to the validation procedure. The tracking id is '1eca50b6-db5b-4c6c-bb25-aea6e847c859'. See inner errors for details. Please see https://aka.ms/arm-deploy for usage details.

This UX is not great, and the link is not really helpful.

Could this link to the Portal showing me the actual deployment? Or better yet, just unwrap the template deployment errors and present them to me along with a link to more details? (In this case, I'm pretty sure it's core quota due to a delete that is still in progress).

Oh, maybe this happening because I'm letting it create the other resources (vnet, etc) so it's doing a template deployment instead of a VM PUT... either way...

[tjprescott]

VM create always does a template deployment. Do you see the error if you run it with --debug?

[colemickens]

Yes. The response does include the real error message inside.

msrest.http_logger : Response status: 400
msrest.http_logger : Response headers:
msrest.http_logger :     'Cache-Control': 'no-cache'
msrest.http_logger :     'Pragma': 'no-cache'
msrest.http_logger :     'Content-Type': 'application/json; charset=utf-8'
msrest.http_logger :     'Expires': '-1'
msrest.http_logger :     'x-ms-failure-cause': 'gateway'
msrest.http_logger :     'x-ms-ratelimit-remaining-subscription-writes': '1199'
msrest.http_logger :     'x-ms-request-id': '653b6ce5-067f-41aa-97a4-e7e0edac638f'
msrest.http_logger :     'x-ms-correlation-request-id': '653b6ce5-067f-41aa-97a4-e7e0edac638f'
msrest.http_logger :     'x-ms-routing-request-id': 'WESTUS2:20180426T191108Z:653b6ce5-067f-41aa-97a4-e7e0edac638f'
msrest.http_logger :     'Strict-Transport-Security': 'max-age=31536000; includeSubDomains'
msrest.http_logger :     'X-Content-Type-Options': 'nosniff'
msrest.http_logger :     'Date': 'Thu, 26 Apr 2018 19:11:07 GMT'
msrest.http_logger :     'Content-Length': '567'
msrest.http_logger : Response content:
msrest.http_logger : b'{"error":{"code":"InvalidTemplateDeployment","message":"The template deployment \'vm_deploy_j3qgP6bySQsDe90g9aXlHvNOiojRJExn\' is not valid according to the validation procedure. The tracking id is \'653b6ce5-067f-41aa-97a4-e7e0edac638f\'. See inner errors for details. Please see https://aka.ms/arm-deploy for usage details.","details":[{"code":"QuotaExceeded","message":"Operation results in exceeding quota limits of Core. Maximum allowed: 20, Current in use: 16, Additional requested: 16. Please read more about quota increase at http://aka.ms/corequotaincrease."}]}}'
msrest.exceptions : The template deployment 'vm_deploy_j3qgP6bySQsDe90g9aXlHvNOiojRJExn' is not valid according to the validation procedure. The tracking id is '653b6ce5-067f-41aa-97a4-e7e0edac638f'. See inner errors for details. Please see https://aka.ms/arm-deploy for usage details.
The template deployment 'vm_deploy_j3qgP6bySQsDe90g9aXlHvNOiojRJExn' is not valid according to the validation procedure. The tracking id is '653b6ce5-067f-41aa-97a4-e7e0edac638f'. See inner errors for details. Please see https://aka.ms/arm-deploy for usage details.

Seems like if the "details" field of the error response was just dumped that it would be useful...

[tjprescott]

Thanks. We have logic like this for the group deployment create command. For our template-based creates, we likely need to apply the same logic.