Improve error diagnostics to help know what to resolve

[timheuer]

• [X] Make sure you've installed the latest version using instructions in the wiki

Output from azd version azd version 0.0.1-beta.1614610 (commit 4d3efcfa5779c24a11379ff53102c3fded786e2e)

Output from az version { "azure-cli": "2.38.0", "azure-cli-core": "2.38.0", "azure-cli-telemetry": "1.0.6", "extensions": { "azure-dev": "0.0.1b1539385", "containerapp": "0.3.7" } }

Describe the bug I created the C# todo template and did azd up -- this is the resulting output:

Created Azure resources
Error: Command Failed: deployment failed: failed deploying: failed running az deployment sub create:

Deployment Error Details:
InternalServerError: There was an unexpected InternalServerError.  Please try again later.  x-ms-correlation-request-id: 52b6e46e-b887-4323-97f4-924f6284c348

The error isn't helpful for me what do know what to do now. Do I run the command again? Do I use the correlation ID to look in portal?

[rajeshkamal5050]

@timheuer did you retry? were you able to proceed further?

@jongio @savannahostrowski Moving it to On Deck. We can pull it into our current milestone based on any further updates.

[timheuer]

No I have not been successful

-th

---

From: Rajesh Kamal @.> Sent: Thursday, August 4, 2022 12:17:35 AM To: Azure/azure-dev @.> Cc: Tim Heuer @.>; Mention @.> Subject: Re: [Azure/azure-dev] Improve error diagnostics to help know what to resolve (Issue #104)

@timheuerhttps://github.com/timheuer did you retry? were you able to proceed further?

@jongiohttps://github.com/jongio @savannahostrowskihttps://github.com/savannahostrowski Moving it to On Deck. We can pull it into our current milestone based on any further updates.

— Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-dev/issues/104#issuecomment-1204862376, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAABFVJV466233EGKTVH7RLVXNVA7ANCNFSM53TNIR3Q. You are receiving this because you were mentioned.Message ID: @.***>

[vhvb1989]

The root cause here was an old azd version installed with npm globally. npm was the way to install azd in the past, and with the new installers, a system can ended up with two azd versions.

Running npm uninstall -g @azure/az-dev-cli helps to remove the old version.

The second issue is related to using upper case for the azd env name, which is WIP and targeted to be part of version 0.1.0-beta.5 on 8/24.

[jongio]

@timheuer you got this working right?

[rajeshkamal5050]

@vhvb1989 and @wbreza worked with @timheuer offline to get this resolved.

Closing this. @timheuer please reopen, if need be.