[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_el7-nightly - Build # 747 - Still Failing!

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_el7-nigh... Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_el7-nigh... Build Number: 747 Build Status: Still Failing Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #718 [parthdhanjal] Updating max click version Changes for Build #719 [parthdhanjal] Updating max click version Changes for Build #720 [parthdhanjal] Updating max click version Changes for Build #721 [parthdhanjal] Updating max click version Changes for Build #722 [parthdhanjal] Updating max click version Changes for Build #723 [parthdhanjal] Updating max click version Changes for Build #724 [parthdhanjal] Updating max click version Changes for Build #725 [parthdhanjal] Updating max click version Changes for Build #726 [parthdhanjal] Updating max click version Changes for Build #727 [parthdhanjal] Updating max click version Changes for Build #728 [parthdhanjal] Updating max click version Changes for Build #729 [parthdhanjal] Updating max click version Changes for Build #730 [parthdhanjal] Updating max click version Changes for Build #731 [parthdhanjal] Updating max click version Changes for Build #732 [parthdhanjal] Updating max click version Changes for Build #733 [parthdhanjal] Updating max click version Changes for Build #734 [parthdhanjal] Updating max click version [Sandro Bonazzola] mock: add centos-stream-9 pre-release for x86_64 Changes for Build #735 [parthdhanjal] Updating max click version Changes for Build #736 [parthdhanjal] Updating max click version Changes for Build #737 [parthdhanjal] Updating max click version Changes for Build #738 [parthdhanjal] Updating max click version Changes for Build #739 [parthdhanjal] Updating max click version Changes for Build #740 [parthdhanjal] Updating max click version Changes for Build #741 [parthdhanjal] Updating max click version Changes for Build #742 [parthdhanjal] Updating max click version Changes for Build #743 [parthdhanjal] Updating max click version Changes for Build #744 [parthdhanjal] Updating max click version Changes for Build #745 [parthdhanjal] Updating max click version Changes for Build #746 [parthdhanjal] Updating max click version Changes for Build #747 [parthdhanjal] Updating max click version ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 008_basic_ui_sanity.start_grid 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 container with name or ID "grid_node_chrome" found: no such container Error response from daemon: no container with name or ID "grid_node_firefox" found: no such container Error response from daemon: no container with name or ID "selenium-hub" found: no such container executing shell: docker kill grid_node_chrome grid_node_firefox selenium-hub Error response from daemon: no container with name or ID "grid_node_chrome" found: no such container Error response from daemon: no container with name or ID "grid_node_firefox" found: no such container Error response from daemon: no container with name or ID "selenium-hub" found: no such container executing shell: docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES executing shell: docker network ls NETWORK ID NAME DRIVER SCOPE 0f2a693e93e2 grid bridge local 2f259bab93aa podman bridge local executing shell: docker network rm grid grid executing shell: docker network ls NETWORK ID NAME DRIVER SCOPE 2f259bab93aa podman bridge local executing shell: docker network ls NETWORK ID NAME DRIVER SCOPE 2f259bab93aa podman bridge local creating docker network for grid executing shell: docker network create grid 0f2a693e93e2ed7008feb5b7714bbab236e3907e64188199e3be1ae367f49c40 executing shell: docker network ls NETWORK ID NAME DRIVER SCOPE 0f2a693e93e2 grid bridge local 2f259bab93aa podman bridge local starting hub executing shell: docker run -d -p 4444:4444 --net grid --name selenium-hub selenium/hub:3.9.1-actinium /usr/bin/docker-current: Error response from daemon: selenium/hub:3.9.1-actinium: image not known. 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_basic-suite-4.3_el7-nightly/ovirt-system-tests/basic-suite-4.3/test-scenarios/008_basic_ui_sanity.py", line 189, 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 container with name or ID "grid_node_chrome" found: no such container Error response from daemon: no container with name or ID "grid_node_firefox" found: no such container Error response from daemon: no container with name or ID "selenium-hub" found: no such container executing shell: docker kill grid_node_chrome grid_node_firefox selenium-hub Error response from daemon: no container with name or ID "grid_node_chrome" found: no such container Error response from daemon: no container with name or ID "grid_node_firefox" found: no such container Error response from daemon: no container with name or ID "selenium-hub" found: no such container executing shell: docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES executing shell: docker network ls NETWORK ID NAME DRIVER SCOPE 0f2a693e93e2 grid bridge local 2f259bab93aa podman bridge local executing shell: docker network rm grid grid executing shell: docker network ls NETWORK ID NAME DRIVER SCOPE 2f259bab93aa podman bridge local executing shell: docker network ls NETWORK ID NAME DRIVER SCOPE 2f259bab93aa podman bridge local creating docker network for grid executing shell: docker network create grid 0f2a693e93e2ed7008feb5b7714bbab236e3907e64188199e3be1ae367f49c40 executing shell: docker network ls NETWORK ID NAME DRIVER SCOPE 0f2a693e93e2 grid bridge local 2f259bab93aa podman bridge local starting hub executing shell: docker run -d -p 4444:4444 --net grid --name selenium-hub selenium/hub:3.9.1-actinium /usr/bin/docker-current: Error response from daemon: selenium/hub:3.9.1-actinium: image not known. See '/usr/bin/docker-current run --help'. getting ip of hub --------------------- >> end captured stdout << ----------------------