- Infra - oVirt List Archives

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

03 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 03 Dec '19

03 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 03 Dec '19

03 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 03 Dec '19

03 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