Azure SDK token POST request on AARCH64 hangs indefinitely. #38077
Labels
Client
This issue points to a problem in the data-plane of the library.
customer-reported
Issues that are reported by GitHub users external to the Azure organization.
needs-team-attention
Workflow: This issue needs attention from Azure service team or SDK team
question
The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Service Attention
Workflow: This issue is responsible by Azure service team.
Storage
Storage Service (Queues, Blobs, Files)
When trying to upload blobs to the azure blob storage on a Linux AARCH64 system, token post hangs indefinitely.
The intention was to use the async azure libraries, specifically the DefaultAzureCredential and BlobServiceClient functions.
Tested using a python script (below) which should authenticate and upload a blob to the blob storage.
The script uses the account name, client ID, tenant ID and azure certificate pem file which contains the certificate and private key. These variables are exported as global ENV variables such that the DefaultAzureCredential can access them.
Once an instance of the DefaultAzureCredential is created (this part is successful), a blob client session is created and subsequently a container client session with the intended container name.
The next step would be to use: container_client.upload_blob function. However before the script gets to this point. During the token request, I get an error message: "no body was attached to the request". And then the program gets stuck indefinitely.
These are the logs from the linux AARCH64 system:
**Note: redacted IDs with *******
There are no further logs after this point, no timeout or exceptions. Just stays there forever.
Using the same script on MacOS, same credentials and inputs, the file upload was a success.
I have created a service request with microsoft, after a call and log review, no solution was found and they suggested I open this ticket.
any idea what's going on?
thank-you!
The text was updated successfully, but these errors were encountered: