fix: increase open websocket handshake timeout
Type of change
-
Bug Fix -
Feature
Does this introduce a change in the core logic?
- [Yes]
Does this introduce a change in the cloud provider implementation, if so which cloud?
-
AWS -
Azure -
GCP -
IBM
Updates description?
The auth phase on Azure is taking longer than 5 seconds and lead to a frequent websocket timeout in the Azure test stage. I am increasing the websocket opening timeout to 30s but the real fix should really to find why it takes more than 5s with the current Azure infrastructure.
You can have a look at the "CLT connect" lines in the "azure_test" stage. ex: https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/reservoir/open-etp-server/-/jobs/1866732 You can see that they sometimes take longer than 5000ms
Edited by Fabien Bosquet