[BUG] Transient issue with mismatch x-ms-client-request-id error occurring when upgrading to Azure.Storage.Blobs v12.15.0

Library name and version

Azure.Storage.Blobs v12.15.0

Describe the bug

A transient issue is occurring where upgrading to v12.15.0 of Azure.Storage.Blobs will cause a transient issue where the following client side SDK error will occur.

Response x-ms-client-request-id '<response-client-request-id>' does not match the original expected request id, '<original-client-request-id>'.

Downgrading to Azure.Storage.Blobs v12.14.1 helps mitigate the issue.

We were not able to get logs to confirm the mismatch in client request id. We were also not able to get a network trace on whether the issue was in a proxy or firewall or cache changing the x-ms-client-request-id.

So far doesn’t seem like the issue is in Azure.Core

Expected behavior

A transient error of mismatch client request id does not occur.

Actual behavior

Mismatch client request id error occurs.

Reproduction Steps

n/a

Call any Storage API

Environment

Azure.Storage.Blobs v12.15.0 AKS cluster

[amnguye]

We’re aiming to see if we can do a release next week with just the change to point at the latest Azure.Core release.

Will update the thread if anything changes.

[amnguye]

@vedion We were actually able to release today. So when available please upgrade to Azure.Storage.Blobs v12.5.1 which points at Azure.Storage.Common v12.14.1 which points at Azure.Core 1.30.