Generic task may ignore response with sessionId or error on org env

[dmtgrinevich]

Session was created in 6m6s

esg-router-2  | time="2023-09-14T13:34:24Z" level=info msg="new request" _uuid=04484706-ef3e-4d7f-813f-63eb74b004c1 family=org-generic remote=54.88.233.5 user=qatests
esg-router-1  | time="2023-09-14T13:35:13Z" level=info msg="new request" _uuid=5fd90021-0e8c-4d0a-925f-b24ec673a977 family=org-linux-edge-latest remote=3.18.119.25 user=qatests
esg-router-1  | time="2023-09-14T13:41:32Z" level=info msg="service started" _taskId=c053dfcf597644c29af67f36740ffcaf _uuid=5fd90021-0e8c-4d0a-925f-b24ec673a977 attempt=2 driver url="http://172.64.4.71:32802/session" family=org-linux-edge-latest remote=3.18.119.25 sessionId=88a486a4849d3c16bcc5c18611ed9f8f user=qatests
esg-router-1  | time="2023-09-14T13:41:32Z" level=debug msg=Response _uuid=5fd90021-0e8c-4d0a-925f-b24ec673a977 family=org-linux-edge-latest remote=3.18.119.25 resp="map[value:map[capabilities:map[acceptInsecureCerts:true browserName:msedge browserVersion:114.0.1823.43 ms:edgeOptions:map[debuggerAddress:localhost:46533] msedge:map[msedgedriverVersion:114.0.1823.43 (ef5b3acd8c1da336e811e5d8552a61c0965816bb) userDataDir:/tmp/.com.microsoft.Edge.F1mGCg] networkConnectionEnabled:false pageLoadStrategy:normal platformName:linux proxy:map[] setWindowRect:true strictFileInteractability:false timeouts:map[implicit:0 pageLoad:300000 script:30000] unhandledPromptBehavior:dismiss and notify webauthn:extension:credBlob:true webauthn:extension:largeBlob:true webauthn:extension:minPinLength:true webauthn:extension:prf:true webauthn:virtualAuthenticators:true] sessionId:5fd90021-0e8c-4d0a-925f-b24ec673a977]]" user=qatests

But response with sessionId was not handled and after 11m (carina's default read_timeout=660), request was canceled by timeout.

[dmtgrinevich]

https://qatests.zebrunner.org/projects/DEF/automation-launches/812068
log.txt
16 sessions failed to start with error org.openqa.selenium.SessionNotCreatedException: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure. , when they (all 16) actually started and were stopped after 1 min by idle timeout
Also these 16 tasks were recreated due to unhealthy status

[dmtgrinevich]

Same run at prod and dev