Azure / Azure/azure-rest-api-specs
Container Deletion returns immediately but the target container is not actually deleted at that time
Nobody has claimed this yet.
- Dominant language
- TypeSpec
- Stars
- 3.1k
- Forks
- 6k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 444
Description
Delete returns immediately but the container is still present and blocks re-use of the name when recreating:
unexpected status 409 (409 Conflict) with error: ContainerOperationFailure: The specified container is being deleted. Try operation later.
The delete response should be returned only when the deletion is complete, or be an LRO with a polling endpoint to be able to confirm the operation is completed successfully rather than requiring users to deal with retry logic on creation.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked specification/storage/resource-manager/Microsoft.Storage/stable/2023-01-01/blob.json at line 363 and inspect the container deletion response definition. Determine how the specification should represent completion or an LRO with polling, then confirm the result allows callers to know when the container can be recreated without handling deletion retries themselves.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, openapi
- Domain
- api, cloud
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100