- Infra - oVirt List Archives

[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 02 Dec '19

02 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 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/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 01 Dec '19

01 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/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

oVirt infra daily report - unstable production jobs - 1025
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/1025//artifact/exported-… Cheers, Jenkins

1 0

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

30 Nov '19

Failed to run project_setup.sh for: #2029 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

oVirt infra daily report - unstable production jobs - 1024
by jenkins＠jenkins.phx.ovirt.org 30 Nov '19

30 Nov '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/1024//artifact/exported-… Cheers, Jenkins

1 0

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

29 Nov '19

Failed to run project_setup.sh for: #15201 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]: 105132,5 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 29 Nov '19

29 Nov '19

Change 105132,5 (vdsm) 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/105132/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17514/

1 0

[CQ]: 104620,10 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 29 Nov '19

29 Nov '19

Change 104620,10 (vdsm) 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/104620/10 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17511/

1 0

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

29 Nov '19

Failed to run project_setup.sh for: #2013 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

[JIRA] (OVIRT-2844) New project - java-client-kubevirt
by Anton Marchukov (oVirt JIRA) 29 Nov '19

29 Nov '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2844?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-2844: -------------------------------------- Assignee: Anton Marchukov (was: infra) > New project - java-client-kubevirt > ---------------------------------- > > Key: OVIRT-2844 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2844 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Piotr Kliczewski > Assignee: Anton Marchukov > > Hi, > I would like to create a new project in upstream gerrit which will host new > engine dependency needed for RHV-CNV integration. ATM the project is hosted > here [1] > Thanks, > Piotr > [1] https://github.com/ahadas/java-client-kubevirt -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

[JIRA] (OVIRT-2844) New project - java-client-kubevirt
by Piotr Kliczewski (oVirt JIRA) 29 Nov '19

29 Nov '19

Piotr Kliczewski created OVIRT-2844: --------------------------------------- Summary: New project - java-client-kubevirt Key: OVIRT-2844 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2844 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Piotr Kliczewski Assignee: infra Hi, I would like to create a new project in upstream gerrit which will host new engine dependency needed for RHV-CNV integration. ATM the project is hosted here [1] Thanks, Piotr [1] https://github.com/ahadas/java-client-kubevirt -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

[CQ]: 105183, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 29 Nov '19

29 Nov '19

A system test invoked by the "ovirt-master" change queue including change 105183,2 (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/105183/2 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/17504/

1 0

[CQ]: 104565, 7 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 29 Nov '19

29 Nov '19

A system test invoked by the "ovirt-master" change queue including change 104565,7 (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/104565/7 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/17502/

1 0

[CQ]: 105171, 1 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 29 Nov '19

29 Nov '19

A system test invoked by the "ovirt-master" change queue including change 105171,1 (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/105171/1 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/17497/

1 0

oVirt infra daily report - unstable production jobs - 1023
by jenkins＠jenkins.phx.ovirt.org 29 Nov '19

29 Nov '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/1023//artifact/exported-… Cheers, Jenkins

1 0

[CQ]: 104201, 8 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Nov '19

28 Nov '19

A system test invoked by the "ovirt-master" change queue including change 104201,8 (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/104201/8 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/17494/

1 0

[CQ]: 104862, 5 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Nov '19

28 Nov '19

A system test invoked by the "ovirt-master" change queue including change 104862,5 (ovirt-system-tests) failed. However, this change seems not to be the root cause for this failure. Change 104858,6 (ovirt-system-tests) 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 104858,6 (ovirt-system-tests) 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/104862/5 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104858/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17490/

1 0

[CQ]: 104858, 6 (ovirt-system-tests) failed "ovirt-master" system tests
by oVirt Jenkins 28 Nov '19

28 Nov '19

Change 104858,6 (ovirt-system-tests) 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/104858/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17486/

1 0

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

28 Nov '19

A system test invoked by the "ovirt-master" change queue including change 105127,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/105127/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/17479/

1 0

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

28 Nov '19

Failed to run project_setup.sh for: #15141 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]: 105140, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Nov '19

28 Nov '19

A system test invoked by the "ovirt-master" change queue including change 105140,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/105140/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/17475/

1 0

[CQ]: 104027, 10 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Nov '19

28 Nov '19

A system test invoked by the "ovirt-master" change queue including change 104027,10 (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/104027/10 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/17471/

1 0

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

28 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/270/ Build Number: 270 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #270 [Galit Rosenthal] Copied master suite sdk4:add_quota_storage_limits [Sandro Bonazzola] change-queues: add ovirt-4.4 queue ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 098_ovirt_provider_ovn.use_ovn_provider_43 Error Message: Fault reason is "Operation Failed". Fault detail is "[Cannot add a Network Interface when VM is not Down, Up or Image-Locked.]". HTTP response code is 409. -------------------- >> begin captured logging << -------------------- requests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:35357 py.warnings: WARNING: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings requests.packages.urllib3.connectionpool: DEBUG: https://192.168.201.4:35357 "POST /v2.0/tokens/ HTTP/1.1" 200 None requests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:9696 requests.packages.urllib3.connectionpool: DEBUG: https://192.168.201.4:9696 "GET /v2.0/networks/ HTTP/1.1" 200 None requests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:9696 requests.packages.urllib3.connectionpool: DEBUG: https://192.168.201.4:9696 "GET /v2.0/ports/ HTTP/1.1" 200 None requests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:9696 requests.packages.urllib3.connectionpool: DEBUG: https://192.168.201.4:9696 "GET /v2.0/subnets/ HTTP/1.1" 200 None requests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:9696 requests.packages.urllib3.connectionpool: DEBUG: https://192.168.201.4:9696 "POST /v2.0/networks/ HTTP/1.1" 201 None requests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:9696 requests.packages.urllib3.connectionpool: DEBUG: https://192.168.201.4:9696 "POST /v2.0/subnets/ HTTP/1.1" 201 None requests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:9696 requests.packages.urllib3.connectionpool: DEBUG: https://192.168.201.4:9696 "POST /v2.0/ports/ HTTP/1.1" 201 None requests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:9696 requests.packages.urllib3.connectionpool: DEBUG: https://192.168.201.4:9696 "GET /v2.0/networks/ HTTP/1.1" 200 None requests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:9696 requests.packages.urllib3.connectionpool: DEBUG: https://192.168.201.4:9696 "GET /v2.0/ports/ HTTP/1.1" 200 None requests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:9696 requests.packages.urllib3.connectionpool: DEBUG: https://192.168.201.4:9696 "GET /v2.0/subnets/ HTTP/1.1" 200 None --------------------- >> end captured logging << --------------------- 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/098_ovirt_provider_ovn.py", line 464, in use_ovn_provider _hotplug_network_to_vm(api, VM0_NAME, NETWORK_1, IFACE_NAME) File "/home/jenkins/agent/workspace/ovirt-system-tests_compat-4.3-suite-master/ovirt-system-tests/compat-4.3-suite-master/test-scenarios/098_ovirt_provider_ovn.py", line 404, in _hotplug_network_to_vm id=profile.id, File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 34352, in add return self._internal_add(nic, headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 232, in _internal_add 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 229, in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 132, in _check_fault self._raise_error(response, body) 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 add a Network Interface when VM is not Down, Up or Image-Locked.]". HTTP response code is 409.\n-------------------- >> begin captured logging << --------------------\nrequests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:35357\npy.warnings: WARNING: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings\n…: DEBUG: https://192.168.201.4:35357 "POST /v2.0/tokens/ HTTP/1.1" 200 None\nrequests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:9696\nrequests.packages.urllib3.connectionpool: DEBUG: https://192.168.201.4:9696 "GET /v2.0/networks/ HTTP/1.1" 200 None\nrequests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:9696\nrequests.packages.urllib3.connectionpool: DEBUG: https://192.168.201.4:9696 "GET /v2.0/ports/ HTTP/1.1" 200 None\nrequests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:9696\nrequests.packages.urllib3.connectionpool: DEBUG: https://192.168.201.4:9696 "GET /v2.0/subnets/ HTTP/1.1" 200 None\nrequests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:9696\nrequests.packages.urllib3.connectionpool: DEBUG: https://192.168.201.4:9696 "POST /v2.0/networks/ HTTP/1.1" 201 None\nrequests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:9696\nrequests.packages.urllib3.connectionpool: DEBUG: https://192.168.201.4:9696 "POST /v2.0/subnets/ HTTP/1.1" 201 None\nrequests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:9696\nrequests.packages.urllib3.connectionpool: DEBUG: https://192.168.201.4:9696 "POST /v2.0/ports/ HTTP/1.1" 201 None\nrequests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:9696\nrequests.packages.urllib3.connectionpool: DEBUG: https://192.168.201.4:9696 "GET /v2.0/networks/ HTTP/1.1" 200 None\nrequests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:9696\nrequests.packages.urllib3.connectionpool: DEBUG: https://192.168.201.4:9696 "GET /v2.0/ports/ HTTP/1.1" 200 None\nrequests.packages.urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): 192.168.201.4:9696\nrequests.packages.urllib3.connectionpool: DEBUG: https://192.168.201.4:9696 "GET /v2.0/subnets/ HTTP/1.1" 200 None\n--------------------- >> end captured logging << ---------------------'

1 1

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

28 Nov '19

Failed to run project_setup.sh for: #15100 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]: 105029, 9 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Nov '19

28 Nov '19

A system test invoked by the "ovirt-master" change queue including change 105029,9 (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/105029/9 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/17466/

1 0

[oVirt Jenkins] deploy-to-gated-ovirt-master - Build #53 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 28 Nov '19

28 Nov '19

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

1 1

[CQ]: 105128,3 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 28 Nov '19

28 Nov '19

Change 105128,3 (vdsm) 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/105128/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17461/

1 0

[CQ]: 104717, 31 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Nov '19

28 Nov '19

A system test invoked by the "ovirt-master" change queue including change 104717,31 (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/104717/31 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/17456/

1 0

[CQ]: 104708, 28 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Nov '19

28 Nov '19

A system test invoked by the "ovirt-master" change queue including change 104708,28 (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/104708/28 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/17451/

1 0

[JENKINS] Failed to setup proejct oVirt_ovirt-web-ui_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 28 Nov '19

28 Nov '19

Failed to run project_setup.sh for: #1087 ovirt-web-ui [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]: 104325, 45 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Nov '19

28 Nov '19

A system test invoked by the "ovirt-master" change queue including change 104325,45 (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/104325/45 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/17445/

1 0

[CQ]: 103956, 33 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Nov '19

28 Nov '19

A system test invoked by the "ovirt-master" change queue including change 103956,33 (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/103956/33 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/17440/

1 0

[JENKINS] Failed to setup proejct ovirt-engine-ui-extensions_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 28 Nov '19

28 Nov '19

Failed to run project_setup.sh for: #307 ovirt-engine-ui-extensions [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