Reputation: 498
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.
Upvotes: 2
Views: 3469
Reputation: 3586
I'm also suffering by this issue today. I'm using azcopy
to copy files from a StorageV2 to StorageV1. I solved this issue by adding --s2s-preserve-access-tier=false
parameter. For example:
azcopy cp "https://[storagev2account].blob.core.windows.net/[container]/?[SAS]" "https://[storagev1account].blob.core.windows.net/events?[SAS]" --recursive=true --s2s-preserve-access-tier=false
Upvotes: 1
Reputation: 1
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).
Upvotes: 0
Reputation: 2513
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.
Upvotes: 0
Reputation: 1
@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
Upvotes: 0
Reputation: 1
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
Upvotes: 0
Reputation: 14088
I have reproduce your error,
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.
Upvotes: 1
Reputation: 19
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://learn.microsoft.com/en-us/azure/storage/common/storage-account-upgrade.
Upvotes: 1