The error message is incorrect when moving files to a non-existed folder in one ADLS Gen2 blob container

microsoft / AzureStorageExplorer

Easily manage the contents of your storage account with Azure Storage Explorer. Upload, download, and manage blobs, files, queues, tables, and Cosmos DB entities. Gain easy access to manage your virtual machine disks. Work with either Azure Resource Manager or classic storage accounts, plus manage and configure cross-origin resource sharing (CORS) rules.

Creative Commons Attribution 4.0 International

377 stars 87 forks source link

The error message is incorrect when moving files to a non-existed folder in one ADLS Gen2 blob container #8201

Open v-kellyluo opened 1 month ago

v-kellyluo commented 1 month ago

Storage Explorer Version: 1.36.0-dev (100) Build Number: 20240925.3 Branch: rel/1.36.0 Platform/OS: Windows11/Windows 10/Linux Ubuntu 22.04/MacOS Sonoma 14.6.1(Apple M1 Pro) Architecture: arm64/x64/x64/x64 How Found: From running test cases Regression From: Previous release (1.35.0)

Steps to Reproduce

Expand one ADLS Gen2 storage account -> Blob Containers.
Create a blob container -> Upload a blob.
Select the blob -> Click 'Move'.
Type a character into the 'Destination directory' field -> Click 'Move'.
Click 'Details...' next to the failed activity log.
Check whether the error message is 'RenameDestinationParentPathNotFound'.

Expected Experience

The error message is 'RenameDestinationParentPathNotFound'.

Actual Experience

The error message is 'AuthorizationPermissionMismatch'.

craxal commented 1 month ago

@v-kellyluo I am not able to reproduce this issue on 1.35.0, on 20240925.3, or on a local build. I get the expected RenameDestinationParentPathNotFound error. Maybe you need to double-check your permissions?

Either way, this is a message from the service, not something we have any control over.

v-kellyluo commented 1 month ago

Hi @craxal , thank you for the update! I can still reproduce this issue on rel branch, here is the record: 8201 In addition, I found that this issue doesn't reproduce if I add myself as owner. In 1.35.0, we don't need to add this access.

craxal commented 1 month ago

@v-kellyluo

Can you provide app logs, please?
Are you also able to remove yourself as owner? Does the problem reproduce when you do so?
Are you using OAuth in both 1.35.0 and the release branch build?

craxal commented 1 month ago

@MRayermannMSFT Also agrees this is not a serious problem. The difference in error message could have something to do with whether OAuth or key is being used, in which case authorization errors can be returned instead of the expected error.

Why different versions would be behaving differently is more of a mystery. Please make absolutely sure you are using the exact same account, the same container, the same credential types, the same blob, and the same input into the destination name.