Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error HttpClient.Timeout of 100 seconds elapsing #420

Open
DaniRieker opened this issue Feb 23, 2024 · 1 comment
Open

Error HttpClient.Timeout of 100 seconds elapsing #420

DaniRieker opened this issue Feb 23, 2024 · 1 comment

Comments

@DaniRieker
Copy link

Hey guys,

sometimes i get an internal Server Error on an update operation on a NetApp Volume, which tells me that the HTTPClient.Timeout of 100 seconds was elapsed.
The errorr looks like this:

│ Error: creating/updating "Resource: (ResourceId \"/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourceGroups/...\" / Api Version \"2022-11-01-preview\")": GET https://management.azure.com/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/providers/Microsoft.NetApp/locations/westeurope/operationResults/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
│ --------------------------------------------------------------------------------
│ RESPONSE 200: 200 OK
│ ERROR CODE: InternalServerError
│ --------------------------------------------------------------------------------
│ {
│   "id": "/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/providers/Microsoft.NetApp/locations/westeurope/operationResults/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
│   "name": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
│   "status": "Failed",
│   "startTime": "2024-02-23T06:07:35.6377976Z",
│   "endTime": "2024-02-23T06:09:27.9996672Z",
│   "percentComplete": 100.0,
│   "properties": {
│     "resourceName": "/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourceGroups/...",
│     "action": "UPDATE"
│   },
│   "error": {
│     "code": "InternalServerError",
│     "message": "The request was canceled due to the configured HttpClient.Timeout of 100 seconds elapsing.",
│     "details": [
│       {
│         "code": "InternalServerError",
│         "message": "The request was canceled due to the configured HttpClient.Timeout of 100 seconds elapsing."
│       }
│     ]
│   }
│ }
│ --------------------------------------------------------------------------------

This one is hard to reproduce, because most of the time the next run of the same deployment doesn't have the problem. I think it is really related to the API sometimes not giving feedback within the configured timeout.

Would it be an option to implement an optional paramter on the provider config to set the HttpClient.Timeout?

@ms-henglu
Copy link
Collaborator

Hi @DaniRieker ,

Thank you for taking time to report this issue!

It seems to be an API issue on the service side, would you please try to contact the Azure Support of this service, they could give a better support on this specific service.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants