[BUG] Storage operations are hanging

[shaibs3]

Library name and version

Azure.Identity 1.12.0

Describe the bug

Azure.Identity version 1.12.0 causes the services to hang upon storage operations
Recently i upgraded the Azure.Identity NuGet from version 1.1.14 to 1.12.0 and started to experience problems when performing io operations vs the storage account (mostly reading and writing blobs). the services depending in this NuGet just hanged and didn't complete their read, write operations. i had to downgrade the NuGet back to 1.1.14 where things work as expected.

Expected behavior

IO operations (read and writing blobs form a storage account) don't hang. i.e calling to BlobClient.OpenWriteAsync will result in a response

Actual behavior

IO operations (read and writing blobs form a storage account) hang. i.e calling to BlobClient.OpenWriteAsync hangs and no response recieved

Reproduction Steps

use azure,identity 1.12.0 and try to read io operations on storage blobs such as BlobClient.OpenWriteAsync, the operation hangs (not all the time)

Environment

No response

[github-actions]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @xgithubtriage.

[PixelByProxy]

I experienced this also, there is a request timeout in Azure.Core as described in this issue #44817

[jsquire]

This was traced back to a bug in Azure.Core which has been fixed in v1.41.0. Until the Storage packages are released with an updated Core reference, mitigation is to take a direct reference to Core in your application.

[github-actions]

Hi @shaibs3. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text "/unresolve" to remove the "issue-addressed" label and continue the conversation.

[github-actions]

Hi @shaibs3, since you haven’t asked that we /unresolve the issue, we’ll close this out. If you believe further discussion is needed, please add a comment /unresolve to reopen the issue.