Closed usrme closed 9 months ago
Thank you for opening this issue, we will look into it.
Seems to have the same issue:
az tag update --resource-id /subscriptions/<subId>/resourceGroups/<rg>/providers/Microsoft.DBforPostgreSQL/flexibleServers/<id> --operation Merge --tags "TEST=OK" -o none
Code: InvalidResourceType
Message: The resource type 'locations/operationResults' could not be found in the namespace 'Microsoft.DBforPostgreSQL' for api version '2022-09-01'. The supported api-versions are '2017-12-01-preview,2017-12-01,2020-02-14-privatepreview,2020-02-14-preview,2020-11-05-preview,2022-03-08-privatepreview,2022-01-20-preview,2021-06-01-preview,2021-06-01,2022-03-08-preview,2022-05-01-privatepreview,2022-05-01-preview,2022-06-01-privatepreview,2022-11-01-preview,2022-12-01,2023-01-01-privatepreview,2023-03-01-preview,2023-06-01-preview,2020-10-05-privatepreview,2022-11-08,2023-03-02-preview'.
AZ version (
azure-cli 2.53.1
core 2.53.1
telemetry 1.1.0
Extensions:
ssh 1.1.6
Dependencies:
msal 1.24.0b2
azure-mgmt-resource 23.1.0b2
The same result also for
az version
{
"azure-cli": "2.49.0",
"azure-cli-core": "2.49.0",
"azure-cli-telemetry": "1.0.8",
"extensions": {
"ssh": "1.1.6"
}
}
Been running into same issue,
"stderr_lines": ["ERROR: (InvalidResourceType) The resource type 'locations/operationResults'
could not be found in the namespace 'Microsoft.DBforPostgreSQL' for api version '2022-09-01'.
The supported api-versions are '2017-12-01-preview,2017-12-01,2020-02-14-privatepreview,
2020-02-14-preview,2020-11-05-preview,2022-03-08-privatepreview,2022-01-20-preview,2021-06-01-
preview,2021-06-01,2022-03-08-preview,2022-05-01-privatepreview,2022-05-01-preview,2022-06-01-
privatepreview,2022-11-01-preview,2022-12-01,2023-01-01-privatepreview,2023-03-01-preview,
2023-06-01-preview,2020-10-05-privatepreview,2022-11-08,2023-03-02-preview'.",
"Code: InvalidResourceType", ...."], "stdout": "", "stdout_lines": []}
Fails az tag
consistently with above error when trying to update tags to following Azure resources:
Not CLI, but I've run into this exact error using Azure.ResourceManager in C#. I've tried it in both West US 2 and East US 2 regions. Azure.ResourceManager 1.8.0 Azure.ResourceManager.Compute 1.2.0
var snapshotResource = await snapshotCollection.CreateOrUpdateAsync(WaitUntil.Completed, snapshotName, snapshotData, cancellationToken);
var tags = new Dictionary<string, string>()
{
{ "Tag A", "Tag Value A" },
{ "Tag B", "Tag Value B" },
{ "Tag C", "Tag Value C" },
};
await snapshotResource.Value.SetTagsAsync(tags, cancellationToken);
Throws the following Exception: Azure.RequestFailedException: 'The resource type 'locations/diskoperations' could not be found in the namespace 'Microsoft.Compute' for api version '2022-09-01'. The supported api-versions are '2016-04-30-preview,2017-03-30,2018-04-01,2018-06-01,2018-09-30,2019-03-01,2019-07-01,2019-11-01,2020-05-01,2020-06-30,2020-09-30,2020-12-01,2021-04-01,2021-08-01,2021-12-01,2022-03-02,2022-07-02,2023-01-02,2023-04-02'. Status: 404 (Not Found) ErrorCode: InvalidResourceType
The code above worked as recently as 30-Oct. I've discovered I can work around it by doing snapshotData.Tags.Add(tag, value) before calling CreateOrUpdateAsync, but the fact that I have to change code that's worked for the past year is more than a bit frustrating.
Same issue here using az cli version 2.53.1.
Message: The resource type 'locations/diskoperations' could not be found in the namespace 'Microsoft.Compute' for api version '2022-09-01'. The supported api-versions are '2016-04-30-preview,2017-03-30,2018-04-01,2018-06-01,2018-09-30,2019-03-01,2019-07-01,2019-11-01,2020-05-01,2020-06-30,2020-09-30,2020-12-01,2021-04-01,2021-08-01,2021-12-01,2022-03-02,2022-07-02,2023-01-02,2023-04-02'.
@yonzhan, any updates?
The Microsoft support said that they are working on a fix, but they didn't give me an ETA.
Same for me. ETA is couple of weeks :/.
So it works with 2.35.0, even if the command output is kind of weird - properties.tags: null
čt 7. 12. 2023 v 10:37 odesílatel Frédéric Husson @.***> napsal:
The Microsoft support said that they are working on a fix, but they didn't give me an ETA.
— Reply to this email directly, view it on GitHub https://github.com/Azure/azure-cli/issues/27745#issuecomment-1845003584, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABLU3GA76FVTLG4SYWVG6WTYIGE5NAVCNFSM6AAAAAA62TWYA6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBVGAYDGNJYGQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>
Hi, I just had a mail from Microsoft support this morning : "the fix has been rolled out in France Central region" I don't have the bug anymore in this region.
Closing as everything seems to be working again as it did before.
Describe the bug
Overnight,
az tag
commands have started to fail in certain locations, such as West US 2 and Sweden Central.Related command
az tag
Errors
Issue script & Debug output
Expected behavior
The tags should be created/modified as usual/as in other regions.
Environment Summary
Additional context
The value for
<Base64 value>
resolves to the following:When executing the exact same command, but from a different location (e.g. France South or Central US) then everything works as expected. We have not changed anything on our side and this was also the case with at least version 2.52.0 of Azure CLI.