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.Storage version 3.4 does not work in AzureGovernment Regions #14395

Closed
mattyt0406 opened this issue Mar 2, 2021 · 4 comments
Closed

Az.Storage version 3.4 does not work in AzureGovernment Regions #14395

mattyt0406 opened this issue Mar 2, 2021 · 4 comments
Labels
customer-reported question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention This issue is responsible by Azure service team. Storage

Comments

@mattyt0406
Copy link

Error after updating Azure Automation to AZ.Storage 3.4 now getting this :
Get-AzStorageAccount : No registered resource provider found for location 'usgovvirginia' and API version '2021-01-01' for type 'storageAccounts'. The supported api-versions are '2020-08-01-preview, 2019-06-01, 2019-04-01, 2018-11-01, 2018-07-01, 2018-03-01-preview, 2018-02-01, 2017-10-01, 2017-06-01, 2016-12-01, 2016-07-01, 2016-05-01, 2016-01-01, 2015-06-15, 2015-05-01-preview'. The supported locations are 'usgoviowa, usgovvirginia, usgovtexas, usgovarizona, usdodeast, usdodcentral'. At line:98 char:7 + $sa = Get-AzStorageAccount -StorageAccountName $storageaccountName -R ... +

This is the same error as :
#8892
@ghost ghost added needs-triage This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that customer-reported labels Mar 2, 2021
@blueww
Copy link
Member

blueww commented Mar 3, 2021 •
edited
Loading

@mattyt0406

Thanks for reporting this issue!

I will contact the server team to check why the new API version 2021-01-01 is not available in AzureGovernment Regions, and update you when get any responds.

Besides that, as a workaround, would you please remove Az.Storage 3.4.0, and install 3.3.0 (3.3.0 is on API version 2019-06-01).

  1. Remove the Az.Storage by :
    uninstall-module Az.storage
  2. install Az.Storage 3.3.0 by:
    Install-Module Az.Storage -RequiredVersion 3.3.0 -Repository PSGallery

@dingmeng-xue dingmeng-xue added Service Attention This issue is responsible by Azure service team. Storage and removed needs-triage This is a new issue that needs to be triaged to the appropriate team. labels Mar 4, 2021
@ghost
Copy link

ghost commented Mar 4, 2021

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @xgithubtriage.

Issue Details

Error after updating Azure Automation to AZ.Storage 3.4 now getting this :
Get-AzStorageAccount : No registered resource provider found for location 'usgovvirginia' and API version '2021-01-01' for type 'storageAccounts'. The supported api-versions are '2020-08-01-preview, 2019-06-01, 2019-04-01, 2018-11-01, 2018-07-01, 2018-03-01-preview, 2018-02-01, 2017-10-01, 2017-06-01, 2016-12-01, 2016-07-01, 2016-05-01, 2016-01-01, 2015-06-15, 2015-05-01-preview'. The supported locations are 'usgoviowa, usgovvirginia, usgovtexas, usgovarizona, usdodeast, usdodcentral'. At line:98 char:7 + $sa = Get-AzStorageAccount -StorageAccountName $storageaccountName -R ... +

This is the same error as :
#8892

Author: mattyt0406
Assignees: -
Labels:

Service Attention, Storage, customer-reported, question
Milestone: -

@Juliehzl Juliehzl mentioned this issue Mar 5, 2021
Closed
@CodeYouMust CodeYouMust mentioned this issue Mar 8, 2021
Closed
1 task
@blueww
Copy link
Member

blueww commented Mar 10, 2021 •
edited
Loading

@mattyt0406
The API version 2021-01-01 should already be enabled on location "usgovvirginia;usgoviowa;usdodeast;usdodcentral;usgovtexas;usgovarizona".
So Az.Storage 3.4.0 should work on these regions. Would you please check?

Besides that, I will contact SRP team to see how to avoid this kind of issue happen again.

@blueww
Copy link
Member

blueww commented Mar 23, 2021

Close as the issue is resolved now.

@blueww blueww closed this as completed Mar 23, 2021
@jiasli jiasli mentioned this issue Sep 23, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
customer-reported question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention This issue is responsible by Azure service team. Storage
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@blueww @mattyt0406 @dingmeng-xue