azure-rest-api-specs
azure-rest-api-specs copied to clipboard
[ARM Tags] incorrect status code 202 at /{scope}/providers/Microsoft.Resources/tags/default
PATCH /{scope}/providers/Microsoft.Resources/tags/default on CRP Disk fails with status code 202 (tried with api-version 2021-04-01 and 2021-01-01, same response)
Same call on virtual machine scope and network interface scope is both good.
swagger (it only allow 200) https://github.com/Azure/azure-rest-api-specs/blob/3ef4bf9/specification/resources/resource-manager/Microsoft.Resources/stable/2021-04-01/resources.json#L4376-L4413
Disk ID: /subscriptions/ec0aa5f7-9e78-40c9-85cd-535c6305b380/resourceGroups/rg-weidxu1/providers/Microsoft.Compute/disks/vm1weidxu_OsDisk_1_fb00d73bec2642cdbe361cea58cb1a8c
request
PATCH https://management.azure.com//subscriptions/ec0aa5f7-9e78-40c9-85cd-535c6305b380/resourceGroups/rg-weidxu1/providers/Microsoft.Compute/disks/vm1weidxu_OsDisk_1_fb00d73bec2642cdbe361cea58cb1a8c/providers/Microsoft.Resources/tags/default?api-version=2021-04-01
Try count: 1
Date:Wed, 17 Aug 2022 02:05:33 GMT
Authorization:REDACTED
Content-Length:63
x-ms-return-client-request-id:true
Content-Type:application/json
x-ms-client-request-id:dbb5edf2-04b3-4a32-abfb-76e5b33ab6e5
Accept:application/json
User-Agent:azsdk-java-com.azure.resourcemanager.resources/2.18.0-beta.1 (17.0.1; Windows 11; 10.0)
63-byte body:
{
"operation" : "Replace",
"properties" : {
"tags" : {
"key1" : "value1"
}
}
}
response (the response looks like an LRO)
202 https://management.azure.com//subscriptions/ec0aa5f7-9e78-40c9-85cd-535c6305b380/resourceGroups/rg-weidxu1/providers/Microsoft.Compute/disks/vm1weidxu_OsDisk_1_fb00d73bec2642cdbe361cea58cb1a8c/providers/Microsoft.Resources/tags/default?api-version=2021-04-01 (2678 ms, 0-byte body)
Cache-Control:no-cache
Pragma:no-cache
Expires:-1
Location:https://management.azure.com/subscriptions/ec0aa5f7-9e78-40c9-85cd-535c6305b380/providers/Microsoft.Compute/locations/westus3/DiskOperations/b8e53ae7-41a5-48c3-adee-d6c2d10bd877?p=ddefb9cd-2984-4659-bea2-89a23e6a6130&monitor=true&api-version=2021-08-01
x-ms-ratelimit-remaining-subscription-writes:1196
x-ms-request-id:23295eb7-60b7-44db-b682-b6bda94f0155
x-ms-correlation-request-id:23295eb7-60b7-44db-b682-b6bda94f0155
x-ms-routing-request-id:SOUTHEASTASIA:20220817T020543Z:23295eb7-60b7-44db-b682-b6bda94f0155
Strict-Transport-Security:max-age=31536000; includeSubDomains
X-Content-Type-Options:nosniff
Date:Wed, 17 Aug 2022 02:05:42 GMT
content-length:0
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @rthorn17.
Issue Details
PATCH /{scope}/providers/Microsoft.Resources/tags/default on CRP Disk fails with status code 202 (tried with api-version 2021-04-01 and 2021-04-01, same response)
Same call on virtual machine scope and network interface scope is both good.
swagger https://github.com/Azure/azure-rest-api-specs/blob/3ef4bf9/specification/resources/resource-manager/Microsoft.Resources/stable/2021-04-01/resources.json#L4376-L4413
Disk ID: /subscriptions/ec0aa5f7-9e78-40c9-85cd-535c6305b380/resourceGroups/rg-weidxu1/providers/Microsoft.Compute/disks/vm1weidxu_OsDisk_1_fb00d73bec2642cdbe361cea58cb1a8c
request
PATCH https://management.azure.com//subscriptions/ec0aa5f7-9e78-40c9-85cd-535c6305b380/resourceGroups/rg-weidxu1/providers/Microsoft.Compute/disks/vm1weidxu_OsDisk_1_fb00d73bec2642cdbe361cea58cb1a8c/providers/Microsoft.Resources/tags/default?api-version=2021-04-01
Try count: 1
Date:Wed, 17 Aug 2022 02:05:33 GMT
Authorization:REDACTED
Content-Length:63
x-ms-return-client-request-id:true
Content-Type:application/json
x-ms-client-request-id:dbb5edf2-04b3-4a32-abfb-76e5b33ab6e5
Accept:application/json
User-Agent:azsdk-java-com.azure.resourcemanager.resources/2.18.0-beta.1 (17.0.1; Windows 11; 10.0)
63-byte body:
{
"operation" : "Replace",
"properties" : {
"tags" : {
"key1" : "value1"
}
}
}
response (the response looks like an LRO)
202 https://management.azure.com//subscriptions/ec0aa5f7-9e78-40c9-85cd-535c6305b380/resourceGroups/rg-weidxu1/providers/Microsoft.Compute/disks/vm1weidxu_OsDisk_1_fb00d73bec2642cdbe361cea58cb1a8c/providers/Microsoft.Resources/tags/default?api-version=2021-04-01 (2678 ms, 0-byte body)
Cache-Control:no-cache
Pragma:no-cache
Expires:-1
Location:https://management.azure.com/subscriptions/ec0aa5f7-9e78-40c9-85cd-535c6305b380/providers/Microsoft.Compute/locations/westus3/DiskOperations/b8e53ae7-41a5-48c3-adee-d6c2d10bd877?p=ddefb9cd-2984-4659-bea2-89a23e6a6130&monitor=true&api-version=2021-08-01
x-ms-ratelimit-remaining-subscription-writes:1196
x-ms-request-id:23295eb7-60b7-44db-b682-b6bda94f0155
x-ms-correlation-request-id:23295eb7-60b7-44db-b682-b6bda94f0155
x-ms-routing-request-id:SOUTHEASTASIA:20220817T020543Z:23295eb7-60b7-44db-b682-b6bda94f0155
Strict-Transport-Security:max-age=31536000; includeSubDomains
X-Content-Type-Options:nosniff
Date:Wed, 17 Aug 2022 02:05:42 GMT
content-length:0
| Author: | weidongxu-microsoft |
|---|---|
| Assignees: | - |
| Labels: |
|
| Milestone: | - |
Hi Team, any update on the above issue?
@rthorn17 would you let us know if we should check with ARM for solution on the tag operation, or we should check with CRP if this request is handled by them under the hood?
Same issue https://github.com/Azure/azure-sdk-for-net/issues/30245#issuecomment-1220060795
@Drewm3 for awareness as well, as I assume the tag operation finally get to the PATCH on disk resource.
Removing the CXP attention label since Service team is already involved in this thread.
ref https://github.com/Azure/azure-rest-api-specs/pull/20494