Build failed in Jenkins: system-sync_mirrors-sac-gluster-ansible-el7-x86_64 #162

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

[CQ]: 102956, 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 102956,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 102717,6 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr

Failed to run project_setup.sh for: #630 kubernetes-nmstate [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 nmstate_kubernetes-nmstate_standard-check-pr

Failed to run project_setup.sh for: #624 kubernetes-nmstate [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 nmstate_kubernetes-nmstate_standard-check-pr

Failed to run project_setup.sh for: #628 kubernetes-nmstate [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 nmstate_kubernetes-nmstate_standard-check-pr

Failed to run project_setup.sh for: #623 kubernetes-nmstate [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 nmstate_kubernetes-nmstate_standard-check-pr

Failed to run project_setup.sh for: #625 kubernetes-nmstate [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 nmstate_kubernetes-nmstate_standard-check-pr

Failed to run project_setup.sh for: #627 kubernetes-nmstate [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

[JIRA] (OVIRT-2796) jenkins.ovirt.org unexpected restart

Dusan Fodor created OVIRT-2796: -- Summary: jenkins.ovirt.org unexpected restart Key: OVIRT-2796 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2796 Project: oVirt - virtualization made easy

[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr

Failed to run project_setup.sh for: #631 kubernetes-nmstate [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]: 103287,3 (vdsm) failed "ovirt-master" system tests

Change 103287,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

[JENKINS] Failed to setup proejct vdsm_master_standard-poll-upstream-sources

Failed to run project_setup.sh for: #16 vdsm [poll-upstream-sources]. 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 vdsm_master_standard-poll-upstream-sources

Failed to run project_setup.sh for: #16 vdsm [poll-upstream-sources]. 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 vdsm_master_standard-poll-upstream-sources

Failed to run project_setup.sh for: #16 vdsm [poll-upstream-sources]. 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 vdsm_master_standard-poll-upstream-sources

Failed to run project_setup.sh for: #16 vdsm [poll-upstream-sources]. 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

Build failed in Jenkins: system-sync_mirrors-sac-gluster-ansible-el7-x86_64 #164

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

Build failed in Jenkins: system-sync_mirrors-sac-gluster-ansible-el7-x86_64 #163

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

[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources

Failed to run project_setup.sh for: #356 ovirt-system-tests [poll-upstream-sources]. 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_master_standard-poll-upstream-sources

Failed to run project_setup.sh for: #356 ovirt-system-tests [poll-upstream-sources]. 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_master_standard-poll-upstream-sources

Failed to run project_setup.sh for: #356 ovirt-system-tests [poll-upstream-sources]. 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_master_standard-poll-upstream-sources

Failed to run project_setup.sh for: #356 ovirt-system-tests [poll-upstream-sources]. 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_master_standard-poll-upstream-sources

Failed to run project_setup.sh for: #356 ovirt-system-tests [poll-upstream-sources]. 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_master_standard-poll-upstream-sources

Failed to run project_setup.sh for: #356 ovirt-system-tests [poll-upstream-sources]. 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 infra daily report - unstable production jobs - 947

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/947//artifact/exported-artifacts/upstream_report.html Cheers, Jenkins

[CQ]: 103298, 1 (ovirt-host) failed "ovirt-master" system tests, but isn't the failure root cause

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

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

Failed to run project_setup.sh for: #5483 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 ovirt-system-tests_standard-check-patch

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