Closed monkpit closed 6 years ago
My quota XML file looks like this:
<qa:browsers xmlns:qa="urn:config.gridrouter.qatools.ru">
<browser name="firefox" defaultVersion="58.0">
<version number="58.0">
<region name="1">
<host name="host1" port="4445" count="1"/>
<host name="host2" port="4445" count="1"/>
</region>
</version>
</browser>
<browser name="chrome" defaultVersion="66.0">
<version number="66.0">
<region name="1">
<host name="host1" port="4445" count="1"/>
<host name="host2" port="4445" count="1"/>
</region>
</version>
</browser>
</qa:browsers>
@monkpit ggr-ui
seems to return correct data. I think there is an issue in connecting Selenoid UI to Ggr UI. Please provide a command - how you are starting Selenoid UI.
--selenoid-uri=http://<loadbalancer>:8889/status
with loadbalancer rule to redirect requests on :8889 to ggr-ui on :8888
EDIT: maybe this is because of extra /status in my command... :(
@monkpit yes, --selenoid-uri
should be without /status
, just --selenoid-uri http://<loadbalancer>:8889
Got it working after a little more effort. Thanks for the response!
I have the following setup...
2 docker hosts running 2 copies of Selenoid, 1 on each host. I have GGR and GGR-UI running with quota XML files specifying each of the 2 hosts as hosts in the XML. The quota XML files are on a volume that is shared to all relevant GGR / GGR-UI containers.
When I point Selenoid-UI at GGR-UI, and open the Selenoid-UI page, it shows the Selenoid status as Red. In the logs for the Selenoid-UI container I see this error repeated:
can't get status (json: cannot unmarshal number into Go value of type selenoid.State)
For reference, this is what is reported by
http://<ggr-ui-url>:8888/status
when a container is running a test in Chrome:And this is what is reported from
/status
when no tests are running:Please let me know if I can provide any further info, or if I should file this issue on the Selenoid-UI page. Thanks!