December 2019 - Infra - oVirt List Archives

[CQ]: 105257,3 (ovirt-imageio) failed "ovirt-master" system tests
by oVirt Jenkins 03 Dec '19

03 Dec '19

Change 105257,3 (ovirt-imageio) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/105257/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17550/

1 0

[JENKINS] Failed to setup proejct ovirt-engine_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 03 Dec '19

03 Dec '19

Failed to run project_setup.sh for: #2208 ovirt-engine [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0009.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct ovirt-engine_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 03 Dec '19

03 Dec '19

Failed to run project_setup.sh for: #2172 ovirt-engine [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0009.workers-phx.ovirt.org.

1 0

Build failed in Jenkins: system-sync_mirrors-centos-sclo-rh-release-7.6-el7-x86_64 #122
by jenkins＠jenkins.phx.ovirt.org 02 Dec '19

02 Dec '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-sclo-rh-release-7.6…> Changes: ------------------------------------------ Started by timer Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-sclo-rh-release-7.6…> No credentials specified > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress --prune http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 6cbb066d15a4751af995329e75d0c99f19fa049c (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 6cbb066d15a4751af995329e75d0c99f19fa049c Commit message: "usrc: disable pusher functionality if it was not imported" > git rev-list --no-walk 6cbb066d15a4751af995329e75d0c99f19fa049c # timeout=10 [system-sync_mirrors-centos-sclo-rh-release-7.6-el7-x86_64] $ /bin/bash -xe /tmp/jenkins2132289302989240617.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-sclo-rh-release-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf + MIRRORS_MP_BASE=/var/www/html/repos + MIRRORS_HTTP_BASE=http://mirrors.phx.ovirt.org/repos + MIRRORS_CACHE=/home/jenkins/mirrors_cache + MAX_LOCK_ATTEMPTS=120 + LOCK_WAIT_INTERVAL=5 + LOCK_BASE=/home/jenkins + OLD_MD_TO_KEEP=100 + HTTP_SELINUX_TYPE=httpd_sys_content_t + HTTP_FILE_MODE=644 + main resync_yum_mirror centos-sclo-rh-release-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror centos-sclo-rh-release-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=centos-sclo-rh-release-7.6-el7 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local sync_needed + mkdir -p /home/jenkins/mirrors_cache + verify_repo_fs centos-sclo-rh-release-7.6-el7 yum + local repo_name=centos-sclo-rh-release-7.6-el7 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/centos-sclo-rh-release-7.6-el7 /var/www/html/repos/yum/centos-sclo-rh-release-7.6-el7/base + check_yum_sync_needed centos-sclo-rh-release-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=centos-sclo-rh-release-7.6-el7 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local p_sync_needed=sync_needed + local reposync_out + echo 'Checking if mirror needs a resync' Checking if mirror needs a resync + rm -rf /home/jenkins/mirrors_cache/centos-sclo-rh-release-7.6-el7 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync centos-sclo-rh-release-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=centos-sclo-rh-release-7.6-el7 ++ local repo_arch=x86_64 ++ local reposync_conf=jenkins/data/mirrors-reposync.conf ++ extra_args=("${@:4}") ++ local extra_args ++ reposync --config=jenkins/data/mirrors-reposync.conf --repoid=centos-sclo-rh-release-7.6-el7 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/centos-sclo-rh-release-7.6-el7/base --norepopath --newest-only --urls --quiet Error setting up repositories: Error making cache directory: /home/jenkins/mirrors_cache/centos-sclo-rh-release-7.6-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-sclo-rh-release-7.6-el7' + reposync_out= Build step 'Execute shell' marked build as failure

1 1

[oVirt Jenkins] ovirt-system-tests_compat-4.3-suite-master - Build # 275 - Failure!
by jenkins＠jenkins.phx.ovirt.org 02 Dec '19

02 Dec '19

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.3-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.3-suite-master/275/ Build Number: 275 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #275 [Dominik Holler] network: Give time for the network update to finish ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 006_migrations.migrate_vm_43 Error Message: Fault reason is "Operation Failed". Fault detail is "[Cannot migrate VM because the VM is in Not Responding status.]". HTTP response code is 409. -------------------- >> begin captured stdout << --------------------- source host: lago-compat-4-3-suite-master-host-1 destination host: lago-compat-4-3-suite-master-host-0 --------------------- >> 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 "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 79, in wrapper prefix.virt_env.engine_vm().get_api(api_ver=4), *args, **kwargs File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/agent/workspace/ovirt-system-tests_compat-4.3-suite-master/ovirt-system-tests/compat-4.3-suite-master/test-scenarios/006_migrations.py", line 90, in migrate_vm host=Host(name=dst_host) File "/home/jenkins/agent/workspace/ovirt-system-tests_compat-4.3-suite-master/ovirt-system-tests/compat-4.3-suite-master/test_utils/__init__.py", line 251, in assert_finished_within func(*args, **kwargs) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 31116, in migrate return self._internal_action(action, 'migrate', None, headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 299, in _internal_action return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait return self._code(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 296, in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 134, in _check_fault self._raise_error(response, body.fault) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error raise error Fault reason is "Operation Failed". Fault detail is "[Cannot migrate VM because the VM is in Not Responding status.]". HTTP response code is 409. -------------------- >> begin captured stdout << --------------------- source host: lago-compat-4-3-suite-master-host-1 destination host: lago-compat-4-3-suite-master-host-0 --------------------- >> end captured stdout << ----------------------

1 1

[CQ]: 105239,2 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 02 Dec '19

02 Dec '19

Change 105239,2 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/105239/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17547/

1 0

[JENKINS] Failed to setup proejct ovirt-imageio_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 02 Dec '19

02 Dec '19

Failed to run project_setup.sh for: #1758 ovirt-imageio [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0009.workers-phx.ovirt.org.

1 0

oVirt infra daily report - unstable production jobs - 1027
by jenkins＠jenkins.phx.ovirt.org 02 Dec '19

02 Dec '19

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/1027//artifact/exported-… Cheers, Jenkins

1 0

[JENKINS] Failed to setup proejct ovirt-engine_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 02 Dec '19

02 Dec '19

Failed to run project_setup.sh for: #2166 ovirt-engine [build-artifacts]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0009.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct ovirt-imageio_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 02 Dec '19

02 Dec '19

Failed to run project_setup.sh for: #1738 ovirt-imageio [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0091.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct ovirt-imageio_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 02 Dec '19

02 Dec '19

Failed to run project_setup.sh for: #1730 ovirt-imageio [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0009.workers-phx.ovirt.org.

1 0

[CQ]: 653b577 (ovirt-ansible-vm-infra) failed "ovirt-master" system tests
by oVirt Jenkins 02 Dec '19

02 Dec '19

Change 653b577 (ovirt-ansible-vm-infra) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://github.com/oVirt/ovirt-ansible-vm-infra/commit/653b577b898f06362a60… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17544/

1 0

[JENKINS] Failed to setup proejct ovirt-engine_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 02 Dec '19

02 Dec '19

Failed to run project_setup.sh for: #2138 ovirt-engine [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0009.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct ovirt-engine_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 02 Dec '19

02 Dec '19

Failed to run project_setup.sh for: #2156 ovirt-engine [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0009.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct ovirt-engine_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 02 Dec '19

02 Dec '19

Failed to run project_setup.sh for: #2122 ovirt-engine [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0009.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct ovirt-engine_standard-on-merge
by jenkins＠jenkins.phx.ovirt.org 02 Dec '19

02 Dec '19

Failed to run project_setup.sh for: #286 ovirt-engine [check-merged]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0009.workers-phx.ovirt.org.

1 0

[CQ]: 105056,6 (jenkins) failed "dummy-master" system tests
by oVirt Jenkins 02 Dec '19

02 Dec '19

Change 105056,6 (jenkins) is probably the reason behind recent system test failures in the "dummy-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/105056/6 For failed test results see: http://jenkins.ovirt.org/job/dummy-master_change-queue-tester/198/

1 0

[oVirt Jenkins] deploy-to-gated-dummy-master - Build #111 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 02 Dec '19

02 Dec '19

Build: http://jenkins.ovirt.org/job/deploy-to-gated-dummy-master/111/ Build Name: #111 Build Status: FAILURE Gerrit change: null - title: null - project: null - branch: null - author: null <null>

1 0

[CQ]: 105056,6 (jenkins) failed "dummy-master" system tests
by oVirt Jenkins 02 Dec '19

02 Dec '19

Change 105056,6 (jenkins) is probably the reason behind recent system test failures in the "dummy-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/105056/6 For failed test results see: https://jenkins-staging.ovirt.org/job/dummy-master_change-queue-tester/431/

1 0

[JENKINS] Failed to setup proejct vdsm_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 02 Dec '19

02 Dec '19

Failed to run project_setup.sh for: #15336 vdsm [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0009.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct oVirt_ovirt-engine-sdk-go_standard-on-ghpush
by jenkins＠jenkins.phx.ovirt.org 02 Dec '19

02 Dec '19

Failed to run project_setup.sh for: #36 ovirt-engine-sdk-go [check-merged]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0009.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct oVirt_ovirt-ansible-image-template_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 02 Dec '19

02 Dec '19

Failed to run project_setup.sh for: #84 ovirt-ansible-image-template [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0009.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct ovirt-engine_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 02 Dec '19

02 Dec '19

Failed to run project_setup.sh for: #2089 ovirt-engine [build-artifacts]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0009.workers-phx.ovirt.org.

1 0

[CQ]: 104605, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 02 Dec '19

02 Dec '19

A system test invoked by the "ovirt-master" change queue including change 104605,3 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 103437,35 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 103437,35 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/104605/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/103437/35 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17535/

1 0

[JENKINS] Failed to setup proejct vdsm_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 02 Dec '19

02 Dec '19

Failed to run project_setup.sh for: #15296 vdsm [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0009.workers-phx.ovirt.org.

1 0

[CQ]: 104978, 5 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 02 Dec '19

02 Dec '19

A system test invoked by the "ovirt-master" change queue including change 104978,5 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 103437,35 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 103437,35 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/104978/5 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/103437/35 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17532/

1 0

[JENKINS] Failed to setup proejct ovirt-imageio_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 01 Dec '19

01 Dec '19

Failed to run project_setup.sh for: #1698 ovirt-imageio [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0009.workers-phx.ovirt.org.

1 0

oVirt infra daily report - unstable production jobs - 1026
by jenkins＠jenkins.phx.ovirt.org 01 Dec '19

01 Dec '19

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/1026//artifact/exported-… Cheers, Jenkins

1 0

[CQ]: 104834, 5 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Dec '19

01 Dec '19

A system test invoked by the "ovirt-master" change queue including change 104834,5 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 103437,35 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 103437,35 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/104834/5 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/103437/35 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17528/

1 0

[JENKINS] Failed to setup proejct vdsm_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 01 Dec '19

01 Dec '19

Failed to run project_setup.sh for: #15235 vdsm [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0009.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct vdsm_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 01 Dec '19

01 Dec '19

Failed to run project_setup.sh for: #15212 vdsm [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0009.workers-phx.ovirt.org.

1 0

[CQ]: 104964, 12 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Dec '19

01 Dec '19

A system test invoked by the "ovirt-master" change queue including change 104964,12 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 103437,35 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 103437,35 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/104964/12 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/103437/35 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17526/

1 0

[oVirt Jenkins] ovirt-system-tests_compat-4.3-suite-master - Build # 273 - Failure!
by jenkins＠jenkins.phx.ovirt.org 30 Nov '19

30 Nov '19

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.3-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.3-suite-master/273/ Build Number: 273 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #273 [Dominik Holler] network: Give time for the network update to finish ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 006_migrations.migrate_vm_43 Error Message: False != True after 600 seconds -------------------- >> begin captured stdout << --------------------- source host: lago-compat-4-3-suite-master-host-1 destination host: lago-compat-4-3-suite-master-host-0 --------------------- >> 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 "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 79, in wrapper prefix.virt_env.engine_vm().get_api(api_ver=4), *args, **kwargs File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/agent/workspace/ovirt-system-tests_compat-4.3-suite-master/ovirt-system-tests/compat-4.3-suite-master/test-scenarios/006_migrations.py", line 90, in migrate_vm host=Host(name=dst_host) File "/home/jenkins/agent/workspace/ovirt-system-tests_compat-4.3-suite-master/ovirt-system-tests/compat-4.3-suite-master/test_utils/__init__.py", line 255, in assert_finished_within timeout File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 278, in assert_true_within assert_equals_within(func, True, timeout, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 252, in assert_equals_within '%s != %s after %s seconds' % (res, value, timeout) False != True after 600 seconds -------------------- >> begin captured stdout << --------------------- source host: lago-compat-4-3-suite-master-host-1 destination host: lago-compat-4-3-suite-master-host-0 --------------------- >> end captured stdout << ----------------------

1 1