microsoft / microsoft/AzureStorageExplorer
Fail to upload one blob with the same name if deleting a blob whose ArchiveStatus is rehydrate-pending-to-hot/cool
Open
Nobody has claimed this yet.
:gear: blobs
:test_tube: testing
:white_check_mark: duplicate
- Dominant language
- No language data
- Stars
- 452
- Forks
- 92
- Avg merge
- 15h 20m
- Merged PRs (30d)
- 3
Description
Storage Explorer Version: 1.23.0-dev
Build Number: 20220127.4
Branch: main
Platform/OS: Windows 10/Linux Ubuntu 20.04/MacOS Big Sur 11.6.1
How Found: Ad-hoc testing
Regression From: Not a regression
Steps to Reproduce
- Expand one storage account -> Blob Containers. (Make sure Soft Delete is enabled)
- Create a blob container -> Upload one blob.
- Chang its access tier to 'Archive' -> Change its access tier to 'Hot'/'Cool'.
- The blob's ArchiveStatus is rehydrate-pending-to-hot/cool.
- Delete the blob -> Upload a blob whose name is the same as the deleted blob.
- Check whether succeeds to upload the blob.
Expected Experience
Succeed to upload the blob.
Actual Experience
Fail to upload the blob.

Additional Context
- This issue doesn't reproduce when the Soft Delete is disabled.
- Related issue: 5034.
Contributor guide
No contributing guide indexed for this repository
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.
Assessment
This issue has not been assessed yet.