locked
No registered resource provider found for location RRS feed

  • Question

  • Command Name
    az acr show

    Errors:

    No registered resource provider found for location 'westeurope' and API version '2019-05-01' for type 'registries'. The supported api-versions are '2016-06-27-preview, 2017-03-01, 2017-10-01, 2017-06-01-preview'. The supported locations are 'westus, eastus, southcentralus, westeurope, northeurope, uksouth, ukwest, australiaeast, australiasoutheast, centralindia, koreacentral, francecentral, southafricanorth, eastasia, japaneast, japanwest, southeastasia, southindia, brazilsouth, canadaeast, canadacentral, centralus, eastus2, northcentralus, westcentralus, westus2'.
    

    To Reproduce:

    Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

    • create azure container registry myacr in resource group myresourcegroup (e.g. through azure portal)
    • az acr show --name myacr --resource-group myresourcegroup --query "id" --output tsv

    Expected Behavior

    It returns the ID of the resource

    Environment Summary

    Linux-5.1.15-arch1-1-ARCH-x86_64-with-arch
    Python 3.7.3
    Shell: bash
    
    azure-cli 2.0.67
    acr 2.2.9
    
    
    Extensions:
    aks-preview 0.4.5
    azure-devops 0.11.0
    
    

    Additional Context

    The issue is not reproducible on every machine. Re-installation of azure-cli with or without extensions does not change anything.


    GH issue: azure-cli/issues/9834

    What is wrong?

    • Edited by carbolymer Monday, July 1, 2019 12:22 PM
    Monday, July 1, 2019 12:21 PM

Answers

  • kobulloc,

    Thank you for your assistance. After upgrade of az-cli to 2.0.68 the issue no longer persists.

    • Marked as answer by carbolymer Thursday, July 11, 2019 4:18 PM
    Thursday, July 11, 2019 4:16 PM

All replies

  • Carbolymer,

    Thank you for using Azure, and thank you again for such an excellent write up!  For anyone else reading this, this is a perfect template example of how to report an issue.

    I haven't been able to reproduce this yet, but it sounds like this isn't happening on every machine.  Before we move forward on this, let's confirm that we've addressed common causes for this error:

    https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-manager-register-provider-errors

    Symptom

    When deploying resource, you may receive the following error code and message:

    Code: NoRegisteredProviderFound Message: No registered resource provider found for location {location} and API version {api-version} for type {resource-type}.

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

    Cause

    You receive these errors for one of these reasons:

    • The required resource provider hasn't been registered for your subscription
    • API version not supported for the resource type
    • Location not supported for the resource type

    Solution

    https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-manager-register-provider-errors#solution-2---azure-cli

    To see whether the provider is registered, use the az provider list command.

    az provider list

    To register a resource provider, use the az provider register command, and specify the namespace to register.

    az provider register --namespace Microsoft.Cdn

    To see the supported locations and API versions for a resource type, use:

    az provider show -n Microsoft.Web --query "resourceTypes[?resourceType=='sites'].locations"

    Additional Troubleshooting

    If that doesn't work, it's possible that updating the Auzre SDK would resolve the issue (although that may not apply to your scenario).

    https://stackoverflow.com/questions/37800291/azure-noregisteredproviderfound-when-creating-database-with-web-app

     

    If you still end up seeing the issue after the troubleshooting above, let me know so we can continue to investigate this.

    Link to the GitHub issue that you mentioned for other readers:

    https://github.com/Azure/azure-cli/issues/9834

    Tuesday, July 2, 2019 4:43 AM
  • Thanks for your reply!

    That's the output from `az provider list` for Microsoft.Cdn: https://github.com/Azure/azure-cli/files/3349153/microsoft.cdn.log

    I don't have enough rights in my subscription to register a new provider.

    Additionally:

    % az provider show -n Microsoft.Cdn --query "resourceTypes[?resourceType=='sites'].locations"
    []

    Regarding, updating Azure SDK, I'm using the latest 4.0.0 already.
    • Edited by carbolymer Tuesday, July 2, 2019 8:55 AM
    Tuesday, July 2, 2019 8:51 AM
  • Carbolymer,

    • For other people who may be reading this, I'm going to propose the first response as an answer as that should cover most scenarios.
    • I'm going to contact the product group to see if we can improve the error message description to give more information to others who may encounter this.
    • For your issue, we're going to need some additional information which I'll request that you email to us directly (instructions below).


    Please email the following to AzCommunity@microsoft.com and we'll get back to you promptly:

     

    - Your Subscription ID (this can be found by searching for "Subscriptions" in the portal

    A link to this thread so we can validate and expedite the request

    A brief, 2-3 sentence summary of your issue

    The person you were working with (kobulloc)

    That would look something like this:

     

    I was working with kobulloc on a CLI issue where we encountered the error, "No registered resource provider found for location...".

     

    Forum Link:

    https://social.msdn.microsoft.com/Forums/en-US/1ecd2eb5-06ec-41ef-8043-c621f37125df/no-registered-resource-provider-found-for-location?forum=azurescripting

     

    Subscription ID:

    aaaaaa-bbbb-cccc-1111-222222222222

    Monday, July 8, 2019 1:42 AM
  • kobulloc,

    Thank you for your assistance. After upgrade of az-cli to 2.0.68 the issue no longer persists.

    • Marked as answer by carbolymer Thursday, July 11, 2019 4:18 PM
    Thursday, July 11, 2019 4:16 PM