Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Latest API version not available in sovereign clouds #23985

Open
jiasli opened this issue Sep 23, 2022 · 12 comments
Open

Latest API version not available in sovereign clouds #23985

jiasli opened this issue Sep 23, 2022 · 12 comments
Assignees
@evelyn-ys
Labels
Azure CLI Team The command of the issue is owned by Azure CLI team common issue Core CLI core infrastructure feature-request
Milestone
Backlog

Comments

@jiasli
Copy link
Member

jiasli commented Sep 23, 2022 •
edited
Loading

Previously reported by

Symptom

We have a centralized location to define API versions for each resource provider:

azure-cli/src/azure-cli-core/azure/cli/core/profiles/_shared.py

Lines 154 to 158 in daa5685

AZURE_API_PROFILES = {
'latest': {
ResourceType.MGMT_STORAGE: '2022-05-01',
ResourceType.MGMT_NETWORK: '2022-01-01',
ResourceType.MGMT_COMPUTE: SDKProfile('2022-03-01', {

Azure CLI supports 4 clouds, including 3 sovereign clouds:

  • AzureCloud
  • AzureChinaCloud
  • AzureUSGovernment
  • AzureGermanCloud

All of them use the same latest profile and the same API version for each resource provider.

However, it happens frequently that a new API version is only deployed to AzureCloud, but not other clouds. Using Azure CLI to call that API version leads to error like:

NoRegisteredProviderFound - No registered resource provider found for location 'chinanorth' and API version '2019-06-15-preview' for type 'profiles/endpoints'. The supported api-versions are '2015-06-01, 2016-04-02, 2016-10-02, 2017-04-02, 2017-10-12, 2018-04-02, 2019-04-15'. The supported locations are 'chinanorth, chinanorth2, chinaeast, chinaeast2'.

Temporary workaroud

Install previous versions of Azure CLI that use old API versions in sovereign clouds. The installation document has detailed instruction on how to install previous versions: https://learn.microsoft.com/en-us/cli/azure/install-azure-cli

Solution

Service team should deploy the new API version to all clouds synchronously.
@yonzhan yonzhan added the Core CLI core infrastructure label Sep 23, 2022
@jiasli jiasli changed the title Latest API version not available in sovereign clouds Latest API version not available in sovereign clouds or certain regions Sep 23, 2022
@jiasli jiasli changed the title Latest API version not available in sovereign clouds or certain regions Latest API version not available in sovereign clouds Sep 23, 2022
@jiasli
Copy link
Member Author

jiasli commented Sep 23, 2022

A similar issue is when a new API version is only deployed to certain regions, but not other regions. This happened for network RP before:

@jiasli
Copy link
Member Author

jiasli commented Sep 23, 2022

Azure PowerShell faces the same issue:

@yonzhan yonzhan added the Azure CLI Team The command of the issue is owned by Azure CLI team label Sep 23, 2022
@jonathanzhang02
Copy link

Hi this happened again in our pipeline, could some actions be taken to ensure API version consistencies in sovereign clouds?

08:53:58  fatal: [127.0.0.1]: FAILED! => {"attempts": 3, "changed": true, "cmd": "az keyvault update  --resource-group \"modelt-tcyz0otvcne\"  --name \"modelt-tcyz0otvcne-vault\"  --default-action Deny\n", "delta": "0:00:02.765346", "end": "2023-04-06 00:53:56.239069", "msg": "non-zero return code", "rc": 1, "start": "2023-04-06 00:53:53.473723", "stderr": "ERROR: (NoRegisteredProviderFound) No registered resource provider found for location 'chinanorth3' and API version '2023-02-01' for type 'vaults'. The supported api-versions are '2015-06-01, 2016-10-01, 2018-02-14-preview, 2018-02-14, 2019-09-01, 2021-04-01-preview, 2021-06-01-preview, 2021-10-01, 2021-11-01-preview, 2022-07-01, 2022-11-01, 2022-02-01'. The supported locations are 'chinanorth, chinaeast, chinanorth2, chinaeast2, chinanorth3, chinaeast3'.\nCode: NoRegisteredProviderFound\nMessage: No registered resource provider found for location 'chinanorth3' and API version '2023-02-01' for type 'vaults'.

@jiasli jiasli mentioned this issue May 10, 2023
Open
@azure-client-tools-bot-prd azure-client-tools-bot-prd bot mentioned this issue Jun 8, 2023
Closed
This was referenced Jul 4, 2023
Closed
Closed
@jinyunma jinyunma mentioned this issue Jul 6, 2023
Merged
@fangchen0601
Copy link
Member

Previously reported by

Symptom

We have a centralized location to define API versions for each resource provider:

azure-cli/src/azure-cli-core/azure/cli/core/profiles/_shared.py

Lines 154 to 158 in daa5685

AZURE_API_PROFILES = {
'latest': {
ResourceType.MGMT_STORAGE: '2022-05-01',
ResourceType.MGMT_NETWORK: '2022-01-01',
ResourceType.MGMT_COMPUTE: SDKProfile('2022-03-01', {

Azure CLI supports 4 clouds, including 3 sovereign clouds:

  • AzureCloud
  • AzureChinaCloud
  • AzureUSGovernment
  • AzureGermanCloud

All of them use the same latest profile and the same API version for each resource provider.

However, it happens frequently that a new API version is only deployed to AzureCloud, but not other clouds. Using Azure CLI to call that API version leads to error like:

NoRegisteredProviderFound - No registered resource provider found for location 'chinanorth' and API version '2019-06-15-preview' for type 'profiles/endpoints'. The supported api-versions are '2015-06-01, 2016-04-02, 2016-10-02, 2017-04-02, 2017-10-12, 2018-04-02, 2019-04-15'. The supported locations are 'chinanorth, chinanorth2, chinaeast, chinaeast2'.

Temporary workaroud

Install previous versions of Azure CLI that use old API versions in sovereign clouds. The installation document has detailed instruction on how to install previous versions: https://learn.microsoft.com/en-us/cli/azure/install-azure-cli

Solution

Service team should deploy the new API version to all clouds synchronously.

Hello,

I am using Azure Portal -> cloud shell, could you suggest how to work around this issue?

@PSanetra
Copy link

Unlike the issue title suggests this issue is not just affecting sovereign clouds, but also the Azure public cloud. See #26813 and #26814

This was referenced Jul 13, 2023
Closed
Closed
Closed
Open
Closed
@GreatState GreatState mentioned this issue Jul 27, 2023
Closed
Closed
@iamalexmang
Copy link

I find it confusing that the bot would link an issue to another issue which is opened relating to sovereign cloud, when the issue I opened earlier is NOT related to sovereign cloud. Either change the title, or stop linking the issues.

Closed
@hobti01
Copy link

hobti01 commented Nov 28, 2023

Looking forward to a resolution for this issue that is still occurring.

ERROR: (NoRegisteredProviderFound) No registered resource provider found for location 'chinanorth3' and API version '2023-10-02-preview' for type 'managedClusters'. The supported api-versions are '2017-08-31, 2018-03-31, 2019-02-01, 2019-04-01, 2019-06-01, 2019-08-01, 2019-10-01, 2019-11-01, 2020-01-01, 2020-02-01, 2020-03-01, 2020-04-01, 2020-06-01, 2020-07-01, 2020-09-01, 2020-11-01, 2020-12-01, 2021-02-01, 2021-03-01, 2021-05-01, 2021-07-01, 2021-08-01, 2021-09-01, 2021-10-01, 2022-01-01, 2022-01-02-preview, 2022-02-01, 2022-03-01, 2022-03-02-preview, 2022-04-01, 2022-04-02-preview, 2022-05-02-preview, 2022-06-01, 2022-06-02-preview, 2022-07-01, 2022-07-02-preview, 2022-08-01, 2022-08-02-preview, 2022-08-03-preview, 2022-09-01, 2022-09-02-preview, 2022-10-02-preview, 2022-11-01, 2022-11-02-preview, 2023-01-01, 2023-01-02-preview, 2023-02-01, 2023-02-02-preview, 2023-03-01, 2023-03-02-preview, 2023-04-01, 2023-04-02-preview, 2023-05-01, 2023-05-02-preview, 2023-06-01, 2023-06-02-preview, 2023-07-01, 2023-07-02-preview, 2023-08-01, 2023-08-02-preview, 2023-09-01, 2023-09-02-preview'. The supported locations are 'chinaeast2, chinanorth2, chinanorth3'.

Using older versions of the az CLI did not resolve the issue, but using an older version of the extension did. az extension list-versions --name aks-preview helped to find the previous version to install with az extension add --name aks-preview --version $AZURE_CLI_AKS_PREVIEW_EXTENSION_VERSION

@jiasli
Copy link
Member Author

jiasli commented Dec 6, 2023

We have an internal ticket IcM 446898172 for this error:

No registered resource provider found for location 'xxx' and API version '2023-10-02-preview' for type 'managedClusters'.

@azure-client-tools-bot-prd azure-client-tools-bot-prd bot mentioned this issue Jan 8, 2024
Closed
@yunbozhang-msft
Copy link
Member

Hi team, what is the progress on this issue?

Open
This was referenced Mar 1, 2024
Open
Open
@michaelschuett-tomtom
Copy link

Still running into this issue.

Open
@IakimLynnyk-TomTom
Copy link

I'm using Azure Dev Ops and facing this issue, how to fix in ADO?

Closed
@ChuckkNorris
Copy link

In case it helps anyone, I was able to resolve this issue (Azure Public cloud) by updating the azurerm version from 3.0.4 to 3.94.0 per this comment: #28499 (comment)

# Configure the Azure provider
terraform {
  required_providers {
    azurerm = {
      source  = "hashicorp/azurerm"
      version = "3.94.0"
    }
  }
  required_version = ">= 1.1.0"
}

Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@evelyn-ys evelyn-ys

Labels
Azure CLI Team The command of the issue is owned by Azure CLI team common issue Core CLI core infrastructure feature-request
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests