Azure / Azure/azure-rest-api-specs
Container Registry Task Run error getting operation result --> Future#WaitForCompletion: the number of retries has been exceeded
- Dominant language
- TypeSpec
- Stars
- 3.1k
- Forks
- 5.9k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 444
Description
This issue is related to #https://github.com/pulumi/pulumi-azure-native/issues/1713
Seems that querying the status of an Azure Container Registry Task.Run operation the url returned inside the `Azure-Asyncoperation` is not correct.
The address provided in that header has the `operationStatuses/` repeated two times.
`https://management.azure.com/.../resourceGroups/crazybike-main-rg/providers/Microsoft.ContainerRegistry/registries/crazybikemaincr/taskRuns/buy-build-task-run/operationStatuses/cb1b/operationStatuses/cb1b?api-version=2019-06-01-preview`
This leads to a 404 not found, the pulumi provider retries some times and then it gives up with the error.
Contributor guide
Research direction
Start with the Azure Container Registry Task.Run specification and the related issue #1713, then trace how the Azure-Asyncoperation URL is represented. Reproduce or inspect the reported URL containing the repeated operationStatuses segment; done means the specification no longer produces that malformed operation-status URL and the 404 scenario is addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, openapi
- Domain
- api, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100