ghost
commented
3 years ago Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @appgwsuppgithub.
Issue Details
## Description This can be steadily reproduced. The LRO state in `/Microsoft.Network/applicationGateways/{name}/start` is inconsistent: - When `/operations/` endpoint returns 200 with `"status": "Succeeded"`, it means polling is finished. And per LRO spec, the `/operationResults` endpoint should return 200/201 as well. - But in reality the `/operationResults` endpoint returns 202 with `Location` header, which normally means the polling is not finished. See below logs for details. ``` POST https://management.azure.com/subscriptions/db1ab6f0-4769-4b27-930e-01e2ef9c123c/resourceGroups/csmrg2075/providers/Microsoft.Network/applicationGateways/azsmnet7653/start?api-version=2021-02-01 HTTP/1.1 Accept: application/json x-ms-client-request-id: 66201da9-13f9-48cd-b889-da5f7ddec5ad x-ms-return-client-request-id: true User-Agent: azsdk-net-ResourceManager.Network/1.0.0-alpha.20211109.1 (.NET Framework 4.8.4420.0; Microsoft Windows 10.0.22000 ) Authorization: xxx Host: management.azure.com Content-Length: 0 HTTP/1.1 200 OK Cache-Control: no-cache Pragma: no-cache Expires: -1 Location: https://management.azure.com/subscriptions/db1ab6f0-4769-4b27-930e-01e2ef9c123c/providers/Microsoft.Network/locations/westus2/operationResults/771d9ca9-d7be-4679-ac48-901c7ff9c344?api-version=2021-02-01 x-ms-request-id: 771d9ca9-d7be-4679-ac48-901c7ff9c344 x-ms-client-request-id: 66201da9-13f9-48cd-b889-da5f7ddec5ad Azure-AsyncOperation: https://management.azure.com/subscriptions/db1ab6f0-4769-4b27-930e-01e2ef9c123c/providers/Microsoft.Network/locations/westus2/operations/771d9ca9-d7be-4679-ac48-901c7ff9c344?api-version=2021-02-01 x-ms-correlation-request-id: fa650dcf-df3c-4999-8654-785b5957d330 x-ms-arm-service-request-id: 05d29ea8-93bc-4d11-9dcd-30f4eb545608 Strict-Transport-Security: max-age=31536000; includeSubDomains Server: Microsoft-HTTPAPI/2.0 Server: Microsoft-HTTPAPI/2.0 x-ms-ratelimit-remaining-subscription-writes: 1199 x-ms-routing-request-id: KOREASOUTH:20211109T160052Z:fa650dcf-df3c-4999-8654-785b5957d330 X-Content-Type-Options: nosniff Date: Tue, 09 Nov 2021 16:00:52 GMT Content-Length: 0 ------------------------------------------------------------------ GET https://management.azure.com/subscriptions/db1ab6f0-4769-4b27-930e-01e2ef9c123c/providers/Microsoft.Network/locations/westus2/operations/771d9ca9-d7be-4679-ac48-901c7ff9c344?api-version=2021-02-01 HTTP/1.1 x-ms-client-request-id: 74f122ad-c6c1-473e-bfe9-ac7e0ddd0824 x-ms-return-client-request-id: true User-Agent: azsdk-net-ResourceManager/1.0.0-beta.5 (.NET Framework 4.8.4420.0; Microsoft Windows 10.0.22000 ) Authorization: xxx Host: management.azure.com Connection: Close HTTP/1.1 200 OK Cache-Control: no-cache Pragma: no-cache Content-Length: 50 Content-Type: application/json; charset=utf-8 Expires: -1 x-ms-request-id: b5902ea3-2f22-499e-a358-2bc0b5cce16c x-ms-client-request-id: 74f122ad-c6c1-473e-bfe9-ac7e0ddd0824 x-ms-correlation-request-id: 3bbe13ea-fd1d-4ade-9f79-c12809b2ac3f x-ms-arm-service-request-id: 2ab96dff-be82-4ad6-b786-2ad1b40f43f7 Strict-Transport-Security: max-age=31536000; includeSubDomains x-ms-ratelimit-remaining-subscription-reads: 11920 Server: Microsoft-HTTPAPI/2.0 Server: Microsoft-HTTPAPI/2.0 x-ms-routing-request-id: KOREASOUTH:20211109T160153Z:3bbe13ea-fd1d-4ade-9f79-c12809b2ac3f X-Content-Type-Options: nosniff Date: Tue, 09 Nov 2021 16:01:53 GMT Connection: close { "status": "Succeeded", "properties": {} } ------------------------------------------------------------------ GET https://management.azure.com/subscriptions/db1ab6f0-4769-4b27-930e-01e2ef9c123c/providers/Microsoft.Network/locations/westus2/operationResults/771d9ca9-d7be-4679-ac48-901c7ff9c344?api-version=2021-02-01 HTTP/1.1 x-ms-client-request-id: 47c3420e-1b3d-4a58-8ed4-2394ea8ef159 x-ms-return-client-request-id: true User-Agent: azsdk-net-ResourceManager/1.0.0-beta.5 (.NET Framework 4.8.4420.0; Microsoft Windows 10.0.22000 ) Authorization: xxxx Host: management.azure.com HTTP/1.1 202 Accepted Cache-Control: no-cache Pragma: no-cache Content-Length: 4 Content-Type: application/json; charset=utf-8 Expires: -1 Location: https://management.azure.com/subscriptions/db1ab6f0-4769-4b27-930e-01e2ef9c123c/providers/Microsoft.Network/locations/westus2/operationResults/771d9ca9-d7be-4679-ac48-901c7ff9c344?api-version=2021-02-01 x-ms-request-id: 771d9ca9-d7be-4679-ac48-901c7ff9c344 x-ms-client-request-id: 66201da9-13f9-48cd-b889-da5f7ddec5ad Azure-AsyncOperation: https://management.azure.com/subscriptions/db1ab6f0-4769-4b27-930e-01e2ef9c123c/providers/Microsoft.Network/locations/westus2/operations/771d9ca9-d7be-4679-ac48-901c7ff9c344?api-version=2021-02-01 x-ms-correlation-request-id: fa650dcf-df3c-4999-8654-785b5957d330 x-ms-arm-service-request-id: 05d29ea8-93bc-4d11-9dcd-30f4eb545608 Strict-Transport-Security: max-age=31536000; includeSubDomains Server: Microsoft-HTTPAPI/2.0 Server: Microsoft-HTTPAPI/2.0 x-ms-ratelimit-remaining-subscription-reads: 11992 x-ms-routing-request-id: KOREASOUTH:20211109T160154Z:39d0b597-32a7-43b0-b813-219a8030fbb7 X-Content-Type-Options: nosniff Date: Tue, 09 Nov 2021 16:01:54 GMT null ------------------------------------------------------------------ ```
| Author: | archerzz |
|---|---|
| Assignees: | - |
| Labels: | `Network - Application Gateway`, `Service Attention` |
| Milestone: | - |
Description
This can be steadily reproduced. The LRO state in
/Microsoft.Network/applicationGateways/{name}/startis inconsistent:/operations/endpoint returns 200 with"status": "Succeeded", it means polling is finished. And per LRO spec, the/operationResultsendpoint should return 200/201 as well./operationResultsendpoint returns 202 withLocationheader, which normally means the polling is not finished.See below logs for details.