Open zzhxiaofeng opened 3 years ago
@zzhxiaofeng Thanks for raising the issue! We will evaluate it.
We welcome contribution to Azurite. It would be great if you could contribute the the fix of this issue.
@blueww, is it possible to increase the priority of this issue? I just ran into this too when trying to set the access tier with a valid lease and getting back a 412 saying There is currently a lease on the blob and no lease ID was specified in the request
(to be clear, the lease ID is specified and valid and the same code works perfectly fine against the Blob Storage live site). Thanks!
@dennisdietrich Thanks for the information! We will priority the fix.
We welcome contribution to Azurite. It would be great if you could contribute the the fix of this issue.
Lease ID is already fixed. Keep the issue open for snapshot fix.
Lease ID fix is already released in v3.11.0.
azsdk-azurite
Error Description: In Azure, it will return error "BlobNotFound" when use Set Blob Tier operation with invalid leaseId or snapshot. But in Azurite, it will set blob tier successfully in this case. Azure error is shown as following:
To Reproduce
Error Track: The reason maybe is that the parameter leaseId and snapshot are not be processed in Blob Set Tier handler method in azurite. The code is shown as following: https://github.com/Azure/Azurite/blob/master/src/blob/handlers/BlobHandler.ts#L872
Expected Behavior When use Set Blob Tier operation with invalid leaseId or snapshot, it doesn't set blob tier successfully and return the error "BlobNotFound".
@jongio for notification.