sometimes getting timeout error when upload

[handhikadj]

Describe the bug

getting it both on iTerm and Terminal. dunno the cause. VPN couldn't help. however if I upload it using the MS Azure Storage Explorer app, the upload succeeds

Command Name az storage blob upload

Errors:

('Connection aborted.', TimeoutError('The write operation timed out'))

To Reproduce:

Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

• az storage blob upload --account-name {} --account-key {} --container-name {} --name {} --file {} --auth-mode {}

Expected Behavior

Upload succeeds

Environment Summary

macOS-12.4-arm64-arm-64bit, Darwin 21.5.0
Python 3.10.4
Installer: HOMEBREW

azure-cli 2.37.0

Additional Context

[yonzhan]

storage service issue

[ghost]

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

Issue Details

---

## Describe the bug getting it both on iTerm and Terminal. dunno the cause. VPN couldn't help. however if I upload it using the MS Azure Storage Explorer app, the upload succeeds **Command Name** `az storage blob upload` **Errors:** ``` ('Connection aborted.', TimeoutError('The write operation timed out')) ``` ## To Reproduce: Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information. - `az storage blob upload --account-name {} --account-key {} --container-name {} --name {} --file {} --auth-mode {}` ## Expected Behavior Upload succeeds ## Environment Summary ``` macOS-12.4-arm64-arm-64bit, Darwin 21.5.0 Python 3.10.4 Installer: HOMEBREW azure-cli 2.37.0 ``` ## Additional Context

Author:	handhikadj
Assignees:	evelyn-ys
Labels:	`Storage`, `Service Attention`, `customer-reported`, `Auto-Assign`
Milestone:	Backlog

[handhikadj]

this issue has yet to be fixed. please fix it ASAP!!! timeout option doesn't work even if I set it to 36000 (10 hours) (--timeout 36000)

[rpbostock]

Was there a reason that the az upload timeout was removed a few months back. This has reintroduced issues that had otherwise been resolved on low bandwidth connections.