Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/258/ Build Number: 258 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #258 [Gal Ben Haim] Add run-ost-container [Evgheni Dereveanchin] Remove fcraw mirror sync job ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 008_basic_ui_sanity.start_grid_42 Error Message: could not get ip address of selenium hub. See previous messages for probable docker failure -------------------- >> begin captured stdout << --------------------- executing shell: docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES executing shell: docker rm -f grid_node_chrome grid_node_firefox selenium-hub Error response from daemon: No such container: grid_node_chrome Error response from daemon: No such container: grid_node_firefox Error response from daemon: No such container: selenium-hub executing shell: docker kill grid_node_chrome grid_node_firefox selenium-hub Error response from daemon: Cannot kill container grid_node_chrome: No such container: grid_node_chrome Error response from daemon: Cannot kill container grid_node_firefox: No such container: grid_node_firefox Error response from daemon: Cannot kill container selenium-hub: No such container: selenium-hub executing shell: docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES executing shell: docker network ls NETWORK ID NAME DRIVER SCOPE 880ec0595692 bridge bridge local 7d05935c9513 host host local 415e4fd8022f none null local executing shell: docker network rm grid Error response from daemon: network grid not found executing shell: docker network ls NETWORK ID NAME DRIVER SCOPE 880ec0595692 bridge bridge local 7d05935c9513 host host local 415e4fd8022f none null local executing shell: docker network ls NETWORK ID NAME DRIVER SCOPE 880ec0595692 bridge bridge local 7d05935c9513 host host local 415e4fd8022f none null local creating docker network for grid executing shell: docker network create grid 5c5927ac45818bb66b200808ae00fe11d3fd92bcc2137cc2f6e26bf9382080d6 executing shell: docker network ls NETWORK ID NAME DRIVER SCOPE 880ec0595692 bridge bridge local 5c5927ac4581 grid bridge local 7d05935c9513 host host local 415e4fd8022f none null local starting hub executing shell: docker run -d -p 4444:4444 --net grid --name selenium-hub selenium/hub:3.9.1-actinium Unable to find image 'selenium/hub:3.9.1-actinium' locally Trying to pull repository docker.io/selenium/hub ... /usr/bin/docker-current: Get https://registry-1.docker.io/v2/selenium/hub/manifests/3.9.1-actinium: Get https://auth.docker.io/token?scope=repository%3Aselenium%2Fhub%3Apull&service=registry.docker.io: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers). See '/usr/bin/docker-current run --help'. getting ip of hub --------------------- >> end captured stdout << ---------------------- Stack Trace: File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test test() File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test-scenarios/008_basic_ui_sanity.py", line 179, in start_grid raise RuntimeError("could not get ip address of selenium hub. See previous messages for probable docker failure") could not get ip address of selenium hub. See previous messages for probable docker failure -------------------- >> begin captured stdout << --------------------- executing shell: docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES executing shell: docker rm -f grid_node_chrome grid_node_firefox selenium-hub Error response from daemon: No such container: grid_node_chrome Error response from daemon: No such container: grid_node_firefox Error response from daemon: No such container: selenium-hub executing shell: docker kill grid_node_chrome grid_node_firefox selenium-hub Error response from daemon: Cannot kill container grid_node_chrome: No such container: grid_node_chrome Error response from daemon: Cannot kill container grid_node_firefox: No such container: grid_node_firefox Error response from daemon: Cannot kill container selenium-hub: No such container: selenium-hub executing shell: docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES executing shell: docker network ls NETWORK ID NAME DRIVER SCOPE 880ec0595692 bridge bridge local 7d05935c9513 host host local 415e4fd8022f none null local executing shell: docker network rm grid Error response from daemon: network grid not found executing shell: docker network ls NETWORK ID NAME DRIVER SCOPE 880ec0595692 bridge bridge local 7d05935c9513 host host local 415e4fd8022f none null local executing shell: docker network ls NETWORK ID NAME DRIVER SCOPE 880ec0595692 bridge bridge local 7d05935c9513 host host local 415e4fd8022f none null local creating docker network for grid executing shell: docker network create grid 5c5927ac45818bb66b200808ae00fe11d3fd92bcc2137cc2f6e26bf9382080d6 executing shell: docker network ls NETWORK ID NAME DRIVER SCOPE 880ec0595692 bridge bridge local 5c5927ac4581 grid bridge local 7d05935c9513 host host local 415e4fd8022f none null local starting hub executing shell: docker run -d -p 4444:4444 --net grid --name selenium-hub selenium/hub:3.9.1-actinium Unable to find image 'selenium/hub:3.9.1-actinium' locally Trying to pull repository docker.io/selenium/hub ... /usr/bin/docker-current: Get https://registry-1.docker.io/v2/selenium/hub/manifests/3.9.1-actinium: Get https://auth.docker.io/token?scope=repository%3Aselenium%2Fhub%3Apull&service=registry.docker.io: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers). See '/usr/bin/docker-current run --help'. getting ip of hub --------------------- >> end captured stdout << ----------------------