az tag update returns an invalid status 'Accepted'
See original GitHub issueThis is autogenerated. Please review and update as needed.
Describe the bug
The tag update command is failing, even though the update is actually succeeding (as indicated by the accepted status).
Command Name
az tag update
Errors:
Operation returned an invalid status 'Accepted'
To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
- Put any pre-requisite steps here…
az tag update --resource-id {} --tags {} --operation {}
Expected Behavior
Environment Summary
macOS-12.4-arm64-arm-64bit, Darwin 21.5.0
Python 3.10.5
Installer: HOMEBREW
azure-cli 2.38.0
Additional Context
Issue Analytics
- State:
- Created a year ago
- Comments:12 (6 by maintainers)
Top Results From Across the Web
Getting invalid status code conflict while running New ...
I am trying to run the below cmdlet in PowerShell and ending up in error : Operation returned invalid status code conflict.
Read more >Azure – Operation returned an invalid status code 'BadRequest'
The command try to create the automation account in “France South” location in the “RG_INFRA” resource group. The error message was not explicit...
Read more >Azure Operation returned an invalid status 'Conflict'
I am having below error while running powershell $thumbprint=$(az webapp config ssl upload --certificate-file ...
Read more >Azure Tagging with Powershell Example
$resource = Get-AzResource -Name AdventureWorksDW -ResourceGroup POC_Resource_Group $tags = @{"costCentre"="000000"} Update-AzTag ...
Read more >Azure Powershell : Operation returned an invalid status code ...
While working on few Azure Powershell scripts I was keep receiving an error 'BadRequest' whenever I was trying to create a new resource...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@zhoxing-ms I sent you the debug log via email. Thanks for looking into this so quickly!
We are seeing the exact same problem with the exact same command (except on Windows), both for Azure CLI 2.34.1 and for 2.38.0. It sounds like this is being worked. If there are any work-arounds in the meantime, it would be really appreciated.