Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Attempts to Upload PageBlobs for BlobStorage and BlockBlobStorage Accounts Don't Appear to Reach Server #1172

Closed
jcrobins opened this issue Feb 28, 2019 · 3 comments
Assignees
Labels
🪲 bug Issue is not intended behavior ⚙️ blobs Related to blob storage ⚙️ data transfer Related to upload, download, copy, etc. ❔ external Root cause of this issue is in another component, product, or service ✅ merged A fix for this issue has been merged
Milestone

Comments

@jcrobins
Copy link

Storage Explorer Version: 1.6.2
Platform/OS Version: Windows
Architecture: ia32
Regression From: N/A

Steps to Reproduce:

  1. Create a Premium BlockBlobStorage (or Standard BlobStorage) storage account.
  2. Select the created storage account in Storage Explorer.
  3. Select a container in this account in Storage Explorer and select Upload > Upload Files... to view the Microsoft Azure Storage Explorer - Upload Files to Blob Container dialog.
  4. Upload a page blob.

Expected Experience:

The operation should result in an error containing the details of the ClientOtherError returned by Storage as a result of issuing a PutBlob of an invalid (PageBlob) type.
The Details of the error should contain the detailed message returned by storage for the failed operation.

Actual Experience:

Server-side logs do not indicate a PutBlob was issued.
The operation eventually fails client-side with the following error details:
{
"message": ""Upload failed unexpectedly after 5 attempt""
}

@jcrobins
Copy link
Author

Semi-Related to the following issue (which requests we remove the "PageBlob" option for BlockBlobStorage and BlobStorage accounts):
#1170

@MRayermannMSFT MRayermannMSFT added this to the 1.8.0 milestone Mar 6, 2019
@MRayermannMSFT MRayermannMSFT added this to Committed in Storage Explorer via automation Mar 6, 2019
@MRayermannMSFT MRayermannMSFT added the 🪲 bug Issue is not intended behavior label Mar 6, 2019
@craxal
Copy link
Contributor

craxal commented Apr 2, 2019

After some investigation, this may be due to the same root cause encountered in #1050. The client library throws an error rather than calling our callback. Since it's an asynchronous situation, a try/catch block won't catch the error as expected.

@craxal craxal added the ❔ investigate We need to look into this further label Apr 2, 2019
@craxal craxal moved this from Committed to Investigating in Storage Explorer Apr 2, 2019
@craxal craxal added the ❔ external Root cause of this issue is in another component, product, or service label Apr 10, 2019
@craxal craxal moved this from Investigating to Blocked in Storage Explorer Apr 10, 2019
@craxal
Copy link
Contributor

craxal commented Apr 17, 2019

Ran quick verification. Appears to be fixed after resolving #1050.

@craxal craxal closed this as completed Apr 17, 2019
Storage Explorer automation moved this from Blocked to Done Apr 17, 2019
@craxal craxal added ✅ merged A fix for this issue has been merged ⚙️ blobs Related to blob storage ⚙️ data transfer Related to upload, download, copy, etc. and removed ❔ investigate We need to look into this further labels Apr 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🪲 bug Issue is not intended behavior ⚙️ blobs Related to blob storage ⚙️ data transfer Related to upload, download, copy, etc. ❔ external Root cause of this issue is in another component, product, or service ✅ merged A fix for this issue has been merged
Projects
Development

No branches or pull requests

3 participants