microsoft / microsoft/AzureStorageExplorer
There is a failed activity log when trying to overwrite an archive blob with soft delete is enabled
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 452
- Forks
- 92
- Avg merge
- 15h 20m
- Merged PRs (30d)
- 3
Description
Storage Explorer Version: 1.20.0
Build Number: 202100630.5
Branch: main
Platform/OS: Windows 10/ Linux Ubuntu 20.04/ MacOS Big Sur 11.4
Architecture: ia32/x64
How Found: Exploratory testing
Regression From: Not a regression
Steps to Reproduce
- Expand one storage account -> Blob Containers (Make sure the soft delete is enabled).
- Create a new blob container -> Upload one blob and set the access tier to 'Archive'.
- Then upload the blob again in any access tier.
- Select 'Replace -> Apply' on the prompt conflict dialog.
- Check whether overwrite successfully or not.
Expected Experience
Overwrite successfully.
Actual Experience
There is a failed activity log.

Additional Context
- Here is the AzCopy log: 404df6a5-2ca1-ec4a-52ee-5eb1d86e8870.log
- Soft delete the archive blob -> Then switch to 'Active and soft deleted blobs' view -> Upload the same blob in any access tier ->Right click on the active blob -> Click 'Manage History -> Manage Snapshots' -> There is a soft-deleted snapshot of the archive blob.

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.
Research direction
Reproduce the overwrite in an Azure Blob container with soft delete enabled and an archive-tier blob. Start by reviewing the linked AzCopy log and the failed activity entry; done means the replacement succeeds without a failed activity log and the resulting blob history matches the expected behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100