microsoft / microsoft/AzureStorageExplorer

Fail to delete or promote ADLS Gen2 snapshots for specific storage accounts

Open
#8,120 3 comments 0 reactions 1 assignee View on GitHub

@craxal is already working on this.

Since Aug 12, 2024.

:test_tube: testing
Dominant language
No language data
Stars
452
Forks
92
Avg merge
15h 20m
Merged PRs (30d)
3

Description

Storage Explorer Version: 1.35.0-dev (100)
Build Number: 20240810.1
Branch: rel/1.35.0
Platform/OS: Windows11/Windows 10/Linux Ubuntu 22.04/MacOS Sonoma 14.6(Apple M1 Pro)
Architecture: arm64/x64/x64/arm64
How Found: From running test cases
Regression From: Not a regression

Steps to Reproduce

  1. Go to the subscription 'StorageExplorer', (I only have the 'Contributor' role for the subscription).
  2. Expand the storage account 'cralvordsnapshot02 (ADLS Gen2)' -> Blob Containers.
  3. Create a blob container -> Upload one blob -> Create one snapshot for the blob.
  4. Go to the snapshots view -> Select one snapshot -> Delete it.
  5. Check whether succeeds to delete the snapshot.

Expected Experience

Succeed to delete the snapshot.

Actual Experience

Fail to delete the snapshot.
image

Error message:

{
  "name": null,
  "message": "\"failed to perform remove command due to error: cannot start job due to error: cannot list files due to reason HEAD https://cralvordsnapshot02.blob.core.windows.net/akristine/file1.txt\\n--------------------------------------------------------------------------------\\nRESPONSE 403: 403 This request is not authorized to perform this operation using this permission.\\nERROR CODE: AuthorizationPermissionMismatch\\n--------------------------------------------------------------------------------\\nResponse contained no body\\n--------------------------------------------------------------------------------\\n.\\n\""
}

Additional Context

Here is the log:
2024-08-12_070931.zip

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.