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

"az keyvault update" not working in Azure China after upgrading to 2.40.0 #23888

Open
jonathanzhang02 opened this issue Sep 14, 2022 · 6 comments
Open

"az keyvault update" not working in Azure China after upgrading to 2.40.0 #23888

jonathanzhang02 opened this issue Sep 14, 2022 · 6 comments
Assignees
@evelyn-ys
Labels
Auto-Assign Auto assign by bot Azure CLI Team The command of the issue is owned by Azure CLI team customer-reported Issues that are reported by GitHub users external to the Azure organization. KeyVault az keyvault question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Milestone
Backlog

Comments

@jonathanzhang02
Copy link

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Related command

% az keyvault update  --resource-group "xxxxxxx"  --name "xxxxxx"  --default-action Deny
(NoRegisteredProviderFound) No registered resource provider found for location 'chinaeast2' and API version '2022-07-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'. The supported locations are 'chinanorth, chinaeast, chinanorth2, chinaeast2, chinanorth3, chinaeast3'.
Code: NoRegisteredProviderFound
Message: No registered resource provider found for location 'chinaeast2' and API version '2022-07-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'. The supported locations are 'chinanorth, chinaeast, chinanorth2, chinaeast2, chinanorth3, chinaeast3'.

Describe the bug
The command az keyvault update --resource-group "xxxxxxx" --name "xxxxxx" --default-action Deny display error message like above after upgrade az to version 2.40.0

To Reproduce
az version 2.40.0 and az keyvault update --resource-group "xxxxxxx" --name "xxxxxx" --default-action Deny

Expected behavior
The command should work on that az version

Environment summary
az command from containerized debian system

Additional context
Please at least give suggestion similar to what was provided in #22735
@ghost ghost added customer-reported Issues that are reported by GitHub users external to the Azure organization. Auto-Assign Auto assign by bot KeyVault az keyvault labels Sep 14, 2022
@ghost ghost assigned evelyn-ys Sep 14, 2022
@ghost ghost added this to the Backlog milestone Sep 14, 2022
@srjennings
Copy link

This happens in GovCloud as well. Running on windows-latest pools.

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

yonzhan commented Sep 14, 2022

@evelyn-ys for awareness

@yonzhan yonzhan added the question The issue doesn't require a change to the product in order to be resolved. Most issues start as that label Sep 14, 2022
@mark-strasser-nnl
Copy link

Also affects az keyvault show in GovCloud.

@evelyn-ys evelyn-ys added the CXP Attention This issue is handled by CXP team. label Sep 16, 2022
@ghost
Copy link

ghost commented Sep 16, 2022

Thank you for your feedback. This has been routed to the support team for assistance.

@evelyn-ys
Copy link
Member

@jlichwa Can you please ask server engineer to deploy 2022-07-01 API version for China Cloud and USGov cloud? Similar issue happens again with #20226

@jonathanzhang02
Copy link
Author

Hi @evelyn-ys and team

Could we have at least a work around here? Our CD pipeline is totally blocked in China.

I tried "az cloud set -n AzureChinaCloud --profile '2020-09-01-hybrid'" and rerun the command, but it still failed.

@jiasli jiasli mentioned this issue Sep 23, 2022
Open
@PramodValavala-MSFT PramodValavala-MSFT removed the CXP Attention This issue is handled by CXP team. label Oct 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@evelyn-ys evelyn-ys

Labels
Auto-Assign Auto assign by bot Azure CLI Team The command of the issue is owned by Azure CLI team customer-reported Issues that are reported by GitHub users external to the Azure organization. KeyVault az keyvault question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
6 participants
@srjennings @evelyn-ys @PramodValavala-MSFT @jonathanzhang02 @mark-strasser-nnl @yonzhan