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.

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

Azure CLI 2.70.0 fails on az storage container generate-sas #31005

Open
wesleyathexagon opened this issue Mar 11, 2025 · 4 comments
Open

Azure CLI 2.70.0 fails on az storage container generate-sas #31005

wesleyathexagon opened this issue Mar 11, 2025 · 4 comments
Assignees
Labels
Auto-Assign Auto assign by bot Auto-Resolve Auto resolve 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. Possible-Solution question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Similar-Issue Storage az storage
Milestone

Comments

@wesleyathexagon
Copy link

Describe the bug

Running a generate-sas command against usgovvirginia from within Azure Pipelines, I'm getting an error.

Related command

az storage container generate-sas --account-name mystorageaccount --account-key $key -n default --https-only --permissions rl --expiry $end -o tsv

Errors

ERROR: (NoRegisteredProviderFound) No registered resource provider found for location 'usgovvirginia' and API version '2024-01-01' for type 'storageAccounts'. The supported api-versions are '2023-05-01, 2023-04-01, 2023-01-01, 2022-09-01, 2022-05-01, 2021-09-01, 2021-08-01, 2021-06-01, 2021-05-01, 2021-04-01, 2021-02-01, 2021-01-01, 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 'usgovvirginia, usgovtexas, usgovarizona, usdodeast, usdodcentral'.
Code: NoRegisteredProviderFound
Message: No registered resource provider found for location 'usgovvirginia' and API version '2024-01-01' for type 'storageAccounts'. The supported api-versions are '2023-05-01, 2023-04-01, 2023-01-01, 2022-09-01, 2022-05-01, 2021-09-01, 2021-08-01, 2021-06-01, 2021-05-01, 2021-04-01, 2021-02-01, 2021-01-01, 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 'usgovvirginia, usgovtexas, usgovarizona, usdodeast, usdodcentral'.
ERROR: argument --account-key: expected one argument

Issue script & Debug output

N/A

Expected behavior

The task should complete successfully as it did in 2.69.0.

Environment Summary

azure-cli 2.70.0

core 2.70.0
telemetry 1.1.0

Extensions:
azure-devops 1.0.1

Dependencies:
msal 1.31.2b1
azure-mgmt-resource 23.1.1

Additional context

No response

@wesleyathexagon wesleyathexagon added the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Mar 11, 2025
Copy link

Hi @wesleyathexagon,

This is a known issue.

Please follow #23985 (comment) to get temporary workaround.

If you feel that further discussion is needed, please add a comment with the text /clibot unresolve to reopen the issue.

@yonzhan
Copy link
Collaborator

yonzhan commented Mar 11, 2025

Thank you for opening this issue, we will look into it.

Copy link

Here are some similar issues that might help you. Please check if they can solve your problem.


Possible solution (Extracted from existing issue, might be incorrect; please verify carefully)

Downgrade the Azure CLI to version 2.19.1 to resolve the issue. This can be done in Azure DevOps pipelines or GitHub actions by specifying the version in the script. For example, in Azure DevOps:

pool:
  vmImage: ubuntu-18.04

- script: |
     sudo apt install -y --allow-downgrades azure-cli=2.19.1-1~bionic

Or in GitHub actions:

uses: azure/CLI@v1
      with:
        azcliversion: 2.19.1
        inlineScript: |

Reference:

Powered by issue-sentinel

@microsoft-github-policy-service microsoft-github-policy-service bot added customer-reported Issues that are reported by GitHub users external to the Azure organization. Storage az storage labels Mar 11, 2025
@microsoft-github-policy-service microsoft-github-policy-service bot added Auto-Assign Auto assign by bot Azure CLI Team The command of the issue is owned by Azure CLI team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Mar 11, 2025
@yonzhan yonzhan removed the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Mar 11, 2025
@yonzhan yonzhan added this to the Backlog milestone Mar 11, 2025
@calvinhzy calvinhzy reopened this Mar 12, 2025
@calvinhzy
Copy link
Member

Hi @wesleyathexagon it is an issue that is currently being fixed on the service side. Will update when it is done. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Assign Auto assign by bot Auto-Resolve Auto resolve 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. Possible-Solution question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Similar-Issue Storage az storage
Projects
None yet
Development

No branches or pull requests

4 participants