[oVirt Jenkins] ovirt-system-tests_performance-suite-master - Build # 789 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_performance-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_performance-suite-master/789/ Build Number: 789 Build Status: Still Failing Triggered By: Started by timer - Changes

Jenkins build is back to normal : system-sync_mirrors-centos-updates-el7-x86_64 #2062

See ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement:

[CQ]: 95000, 2 (ovirt-provider-ovn) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 95000,2 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 94935,3 (ovirt-provider-ovn) that this change depends on or is based on, was detected as the cause of the

[JENKINS] Failed to setup proejct kubevirt_common-templates_standard-check-pr

Failed to run project_setup.sh for: #118 common-templates [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

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 807 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/807/ Build Number: 807 Build Status: Still Failing Triggered By: Started by timer - Changes Since

[oVirt Jenkins] ovirt-node-ng_4.2_build-artifacts-el7-x86_64 - Build # 237 - Fixed!

Project: http://jenkins.ovirt.org/job/ovirt-node-ng_4.2_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-node-ng_4.2_build-artifacts-el7-x86_64/237/ Build Number: 237 Build Status: Fixed Triggered By: Started by timer - Changes Since

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[oVirt Jenkins] ovirt-system-tests_compat-4.1-suite-master - Build # 276 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.1-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.1-suite-master/276/ Build Number: 276 Build Status: Still Failing Triggered By: Started by timer - Changes

[oVirt Jenkins] ovirt-system-tests_compat-4.0-suite-master - Build # 276 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.0-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.0-suite-master/276/ Build Number: 276 Build Status: Still Failing Triggered By: Started by timer - Changes

[oVirt Jenkins] ovirt-system-tests_compat-4.2-suite-master - Build # 276 - Still Failing!

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/276/ Build Number: 276 Build Status: Still Failing Triggered By: Started by timer - Changes

[CQ]: 95000, 2 (ovirt-provider-ovn) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 95000,2 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 94935,3 (ovirt-provider-ovn) that this change depends on or is based on, was detected as the cause of the

[oVirt Jenkins] ovirt-system-tests_network-suite-master - Build # 689 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-master/689/ Build Number: 689 Build Status: Still Failing Triggered By: Started by timer - Changes Since Last

[oVirt Jenkins] ovirt-node-ng-image_master_build-artifacts-fc28-x86_64 - Build # 92 - Failure!

Project: http://jenkins.ovirt.org/job/ovirt-node-ng-image_master_build-artifacts-fc28-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-node-ng-image_master_build-artifacts-fc28-x86_64/92/ Build Number: 92 Build Status: Failure Triggered By: Started by timer

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 587 - Fixed!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/587/ Build Number: 587 Build Status: Fixed Triggered By: Started by timer - Changes Since Last Success:

[oVirt Jenkins] ovirt-system-tests_he-basic-ansible-suite-master - Build # 743 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-master/743/ Build Number: 743 Build Status: Still Failing Triggered By: Started by timer -

[oVirt Jenkins] ovirt-node-ng-image_master_build-artifacts-el7-x86_64 - Build # 91 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-node-ng-image_master_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-node-ng-image_master_build-artifacts-el7-x86_64/91/ Build Number: 91 Build Status: Still Failing Triggered By: Started by timer

Re: [ OST Failure Report ] [ oVirt master (ovirt-engine) ] [ 18-10-2018 ] [ 002_bootstrap.add_hosts ]

openvswitch2.10 was tagged and Gal just merged: https://gerrit.ovirt.org/#/c/95014/ I re-triggered latest changes from failed projects and will update once I see results. thanks, Dafna On Sun, Oct 21, 2018 at 12:29 PM Dafna Ron wrote: > sandro was away for a few days. maybe eyal or Rafael

[oVirt Jenkins] ovirt-appliance_master_build-artifacts-el7-x86_64 - Build # 957 - Fixed!

Project: http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86_64/957/ Build Number: 957 Build Status: Fixed Triggered By: Started by timer -

[oVirt Jenkins] ovirt-system-tests_network-suite-master - Build # 690 - Fixed!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-master/690/ Build Number: 690 Build Status: Fixed Triggered By: Started by timer - Changes Since Last Success:

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #2063

See -- Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace

[oVirt Jenkins] ovirt-system-tests_compat-4.2-suite-master - Build # 277 - Fixed!

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/277/ Build Number: 277 Build Status: Fixed Triggered By: Started by timer - Changes Since Last

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[CQ]: 94732, 7 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 94732,7 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 94841,7 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change

[CQ]: 95038, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 95038,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 94567,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

[CQ]: f86dbef (ovirt-ansible-engine-setup) failed "ovirt-master" system tests

Change f86dbef (ovirt-ansible-engine-setup) 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

[oVirt Jenkins] ovirt-system-tests_performance-suite-master - Build # 790 - Fixed!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_performance-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_performance-suite-master/790/ Build Number: 790 Build Status: Fixed Triggered By: Started by timer - Changes Since Last

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 808 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/808/ Build Number: 808 Build Status: Still Failing Triggered By: Started by timer - Changes Since

[oVirt Jenkins] ovirt-system-tests_he-basic-ansible-suite-master - Build # 744 - Fixed!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-master/744/ Build Number: 744 Build Status: Fixed Triggered By: Started by timer - Changes

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-4.2 - Build # 425 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-4.2/425/ Build Number: 425 Build Status: Still Failing Triggered By: Started by timer - Changes

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-master - Build # 634 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master/634/ Build Number: 634 Build Status: Still Failing Triggered By: Started by timer -

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-master - Build # 492 - Failure!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/492/ Build Number: 492 Build Status: Failure Triggered By: Started by timer - Changes Since Last

[oVirt Jenkins] ovirt-system-tests_he-basic-suite-master - Build # 909 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/909/ Build Number: 909 Build Status: Still Failing Triggered By: Started by timer - Changes Since

[oVirt Jenkins] ovirt-system-tests_compat-3.6-suite-master - Build # 278 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-3.6-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-3.6-suite-master/278/ Build Number: 278 Build Status: Still Failing Triggered By: Started by timer - Changes

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #2049 ovirt-system-tests [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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[CQ]: 93852, 2 (ovirt-imageio) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 93852,2 (ovirt-imageio) failed. However, this change seems not to be the root cause for this failure. Change 94243,5 (ovirt-imageio) that this change depends on or is based on, was detected as the cause of the testing

Re: [CQ]: 95049, 1 (ovirt-hosted-engine-setup) failed "ovirt-4.2" system tests

it seems to have been some networking issue. re-triggered this change. Evgheni, was there anything going on during that time? RepoError: Cannot find a valid baseurl for repo: base/7/x86_64 On Mon, Oct 22, 2018 at 11:24 AM oVirt Jenkins wrote: > Change 95049,1 (ovirt-hosted-engine-setup) is

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-master - Build # 490 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/490/ Build Number: 490 Build Status: Still Failing Triggered By: Started by timer - Changes

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-4.2 - Build # 424 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-4.2/424/ Build Number: 424 Build Status: Still Failing Triggered By: Started by timer - Changes Since Last

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

Re: [ovirt-devel] Re: [ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 14-09-2018 ] [ 002_bootstrap.add_hosts ]

Hi, I hit this problem again. Otopi sends many zero bytes before a response. This time, on an engine installed from master RPM, not dev environment. The engine and host machines are latest Centos 7. Is there some workaround for deploying the host? Thanks, Andrej On Thu, 20 Sep 2018 at 08:59,

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-4.2 - Build # 423 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-4.2/423/ Build Number: 423 Build Status: Still Failing Triggered By: Started by timer - Changes

[oVirt Jenkins] ovirt-system-tests_he-basic-suite-master - Build # 907 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/907/ Build Number: 907 Build Status: Still Failing Triggered By: Started by timer - Changes Since

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[CQ]: 93881, 4 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 93881,4 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 94567,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[oVirt Jenkins] ovirt-system-tests_compat-3.6-suite-master - Build # 276 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-3.6-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-3.6-suite-master/276/ Build Number: 276 Build Status: Still Failing Triggered By: Started by timer - Changes

[JIRA] (OVIRT-2553) add memory to resources

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgheni Dereveanchin reassigned OVIRT-2553: --- Assignee: Evgheni Dereveanchin (was: infra) > add memory to resources >

[JIRA] (OVIRT-2553) add memory to resources

Evgheni Dereveanchin created OVIRT-2553: --- Summary: add memory to resources Key: OVIRT-2553 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2553 Project: oVirt - virtualization made easy

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[oVirt Jenkins] ovirt-system-tests_he-basic-suite-4.2 - Build # 681 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.2/681/ Build Number: 681 Build Status: Still Failing Triggered By: Started by timer - Changes Since Last

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[CQ]: 95049, 1 (ovirt-hosted-engine-setup) failed "ovirt-4.2" system tests

Change 95049,1 (ovirt-hosted-engine-setup) is probably the reason behind recent system test failures in the "ovirt-4.2" 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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-master - Build # 632 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master/632/ Build Number: 632 Build Status: Still Failing Triggered By: Started by timer -

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

  1   2   >