Cannot upload files to Azure General purpose V1 type storage account

2
votes

I have a General Purpose V1 type storage account. I'm trying to upload a file to a container within this account in Azure portal and get the below error.

Block blob commit to blob store failed. Details: StatusCode = 400, StatusText = >Blob access tier is not supported on this storage account type."

I understand that V1 type storage account does not have tier (hot/cold) capabilities, so I would like to know how I can upload a file to V1 type account? The upload dialog in the portal has hot, cold & archive and it looks to be a mandatory parameter.

Note: I was able to upload files successfully until few days back.

6
azureazure-storage-blobs
Hi, have you meet this error before? – Bowman Zhu
No, haven't seen this error before. I was upload files until few days back. – museshad
Please edit your question and include the code. Also tell us which version of SDK are you using? – Gaurav Mantri
No SDK. I'm trying to upload via the Azure portal into the container. – museshad
No, it is no matter with the SDK. – Bowman Zhu

6 Answers

1
votes

I have reproduce your error,

enter image description here

But this doesn't matter, you still can upload files using code. This seems something error with portal. It give a properties named access tier to 'hot'. But v1 type Storage doesn't support the 'hot' access tier(you know this feature). When you upload from code. This situation will not appear.

1
votes

I just ran into the same issue this morning, after messing around with my other accounts I realised that only the v1 storage accounts were giving this error.

The solution for me was upgrading the storage account to V2: https://docs.microsoft.com/en-us/azure/storage/common/storage-account-upgrade.

  1. Sign in to the Azure portal.
  2. Navigate to your storage account.
  3. In the Settings section, click Configuration.
  4. Under Account kind, click on Upgrade.
  5. Under Confirm upgrade, type in the name of your account.
  6. Click Upgrade at the bottom of the blade.
0
votes

Folks, Thanks for bringing it to our attention. We are rolling out a hotfix to fix this issue. In the interim, please use this URL to unblock yourself: https://portal.azure.com/?feature.canmodifystamps=true&Microsoft_Azure_Storage=lastknowngoodbuild

0
votes

@Keith: Please try the URL I provided now. It should work, we've verified the LKGBuild URL should work: https://portal.azure.com/?feature.canmodifystamps=true&Microsoft_Azure_Storage=lastknowngoodbuild

0
votes

Update: Issue has now been resolved.

A hotfix was deployed, i tested and it's working as normal again.

Work Around:

I reported the bug internally as well, Please use Azure Storage Explorer for the time being, I tried and it currently works: https://azure.microsoft.com/en-us/features/storage-explorer/

Let me know if this helps, I'll keep you posted once a solution is rolled out.

0
votes

The Hotfix was deployed yesterday and you should no longer see this issue on the Portal (even if you don't use the LKG URL I provided yesterday).