aerokube/ggr-ui

Selenoid UI not showing running sessions when GGR-UI failed to obtain status of a machine when it is down

hemanthvenkata opened this issue · 1 comments

hemanthvenkata commented

Scenario:

  • Machine A and Machine B added to quota test.xml
  • started ggr, ggr-ui, selenoid-ui and selenoid(on both machines)
  • everything looks good and I am able to see everything green in selenoid-ui

screen shot 2018-08-15 at 7 04 05 pm

screen shot 2018-08-15 at 7 04 52 pm

  • Now let's say Machine B(which has IE and Edge) is down for some reason

screen shot 2018-08-15 at 7 05 51 pm

  • In selenoid UI it shows SELENOID as red(But I am able to execute the tests on other machines which are up and running like on chrome browser)

screen shot 2018-08-15 at 7 06 07 pm

Log details:

Docker image versions: latest-release for all images
Docker version : Docker version 1.13.1-cs2, build ad32da7
GGR-UI error : 2018/08/15 17:04:25 [STATUS] [Failed to fetch status: Get http://ip:4444/status: context canceled] [172.17.0.1]
selenoid-UI error: 2018/08/15 17:02:00 can't get status (Get http://ip:8888/status: context deadline exceeded)

vania-pooh commented

@hemanthvenkata this can be fixed by adjusting SelenoidUI and GgrUI -timeout flags. In GgrUI default timeout is 30s whereas for SelenoidUI default value is 3s. So setting GgrUI -timeout a bit smaller than SelenoidUI -timeout should fix the issue.