Skip to content

Latest commit

 

History

History
84 lines (59 loc) · 3.26 KB

troubleshooting.md

File metadata and controls

84 lines (59 loc) · 3.26 KB

Troubleshooting

This document helps with troubleshooting RWA deployment challenges.

Error: no project exists; to create a new project, run 'azd init'

This error is most often reported when users try to run azd commands before running the cd command to switch to the directory where the repo was cloned.

Workaround

Verify that you are in the directory where the azure.yaml file is located. You may need to cd into the directory to proceed.

BadRequest: Azure subscription is not registered with CDN Provider.

This error message surfaces from the azd provision command when trying to follow the guide to provision an Azure Front Door.

Most Azure resource providers are registered automatically by the Microsoft Azure portal or the command-line interface, but not all. If you haven't used a particular resource provider before, you might need to register that provider.

Full error message

ERROR: deployment failed: error deploying infrastructure: failed deploying: deploying to subscription:

Deployment Error Details:
BadRequest: Azure subscription is not registered with CDN Provider.

Workaround

  1. Register the provider

    az provider register --namespace Microsoft.Cdn

  2. Wait for the registration process to complete (waited about 3-min)

  3. Run the following to confirm the provider is registered

    az provider list --query "[? namespace=='Microsoft.Cdn'].id"

    You should see a notice that the operation succeeded:

    [
"/subscriptions/{subscriptionId}/providers/Microsoft.Cdn"
]

Warning: Remote host identification has changed

This warning message is displayed when the SSH key fingerprint for the remote host has changed since the last time you connected. This can happen if you have re-provisioned the environment which will recreate the VMs and thus their fingerprints.

Full warning message

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!

Workaround

  1. Remove the previous fingerprint which is stored in a file called known_hosts in your user's .ssh directory. Run the following command to remove the old fingerprint: 
    ssh-keygen -R [127.0.0.1]:50022

The deployment already exists in location

This error most often happens when trying a new region with the same for a deployment with the same name used for the AZD environment name (e.g. by default it would be dotnetwebapp).

When the azd provision command runs it creates a deployment resource in your subscription. You must delete this deployment before you can change the Azure region.

Workaround

The following steps assume you are logged in with az cli.

  1. Find the name of the Deployment you want to delete

    az deployment sub list --query "[].name" -o tsv

  2. Delete the deployment by name

    az deployment sub delete -n <deployment-name>

  3. You should now be able to run the azd provision command and resume your deployment.