[JIRA] (OVIRT-2791) mirrors.phx returns 404 when accessing metadata

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dusan Fodor updated OVIRT-2791: --- Resolution: Fixed Status: Done (was: To Do) The patch [1] indeed helped with the issue,

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

Failed to run project_setup.sh for: #572 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: #572 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]: 79a3ea7 (ovirt-web-ui) failed "ovirt-master" system tests

Change 79a3ea7 (ovirt-web-ui) 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

[JIRA] (OVIRT-2792) Error running global_setup.sh with metrics suite

Evgeny Slutsky created OVIRT-2792: - Summary: Error running global_setup.sh with metrics suite Key: OVIRT-2792 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2792 Project: oVirt - virtualization

[JIRA] (OVIRT-2793) ansiblize resources.ovirt.org

Evgheni Dereveanchin created OVIRT-2793: --- Summary: ansiblize resources.ovirt.org Key: OVIRT-2793 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2793 Project: oVirt - virtualization made easy

[CQ]: 103075,1 (vdsm) failed "ovirt-4.3" system tests

Change 103075,1 (vdsm) is probably the reason behind recent system test failures in the "ovirt-4.3" 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

[CQ]: 4d92421 (ovirt-ansible-cluster-upgrade) failed "ovirt-4.2" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-4.2" change queue including change 4d92421 (ovirt-ansible-cluster-upgrade) failed. However, this change seems not to be the root cause for this failure. Change 7aa8be7 (ovirt-ansible-cluster-upgrade) that this change depends on or is based on, was detected as

[CQ]: 79a3ea7 (ovirt-web-ui) failed "ovirt-4.2" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-4.2" change queue including change 79a3ea7 (ovirt-web-ui) failed. However, this change seems not to be the root cause for this failure. Change 66bcd08 (ovirt-web-ui) 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: #5433 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

[CQ]: 102639,10 (vdsm) failed "ovirt-master" system tests

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

[JIRA] (OVIRT-2794) OST is broken since this morning - looks like infra issue

Nir Soffer created OVIRT-2794: - Summary: OST is broken since this morning - looks like infra issue Key: OVIRT-2794 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2794 Project: oVirt - virtualization

[CQ]: 103086,1 (ovirt-release) failed "ovirt-4.3" system tests

Change 103086,1 (ovirt-release) is probably the reason behind recent system test failures in the "ovirt-4.3" 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

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

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

oVirt infra daily report - unstable production jobs - 939

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

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

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

[CQ]: 103072, 3 (vdsm) failed "ovirt-4.3" system tests, but isn't the failure root cause

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

[oVirt Jenkins] ovirt-system-tests_compat-4.3-suite-master - Build # 185 - Still Failing!

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

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

Failed to run project_setup.sh for: #347 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: #347 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: #347 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: #347 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: #347 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: #347 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: #347 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: #347 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: #347 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_standard-check-patch

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

[CQ]: 103087, 1 (ovirt-release) failed "ovirt-4.3" system tests, but isn't the failure root cause

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

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

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

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

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

[JIRA] (OVIRT-2790) Jenkins: build manual trigger rights for asocha

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39788#comment-39788 ] Barak Korren commented on OVIRT-2790: - [~accountid:557058:7013bb8c-48b2-4b9b-898e-eccf5fb61fad] {{ci test

[JIRA] (OVIRT-2788) CI: Add the option to send and email if stage fails

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39789#comment-39789 ] Barak Korren commented on OVIRT-2788: - its not something you can define ATM.

[JIRA] (OVIRT-2791) mirrors.phx returns 404 when accessing metadata

Dusan Fodor created OVIRT-2791: -- Summary: mirrors.phx returns 404 when accessing metadata Key: OVIRT-2791 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2791 Project: oVirt - virtualization made easy

[CQ]: 103030, 4 (ovirt-provider-ovn) failed "ovirt-4.3" system tests, but isn't the failure root cause

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

[JIRA] (OVIRT-2791) mirrors.phx returns 404 when accessing metadata

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39790#comment-39790 ] Ehud Yonasi commented on OVIRT-2791: Patch \[1] was merged today, try re-running the manual job again.

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

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

[CQ]: 5665964 (ovirt-ansible-vm-infra) failed "ovirt-4.2" system tests

Change 5665964 (ovirt-ansible-vm-infra) 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 ovirt-system-tests_standard-check-patch

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

Failed to run project_setup.sh for: #89. 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` project is now gated

Hi everyone, Since we merged one of the more significant patches for enabling patch gating yesterday, the `jenkins` repository is using the gating system as a showcase for this functionality. What this means in practice is that patches should no longer be

[JIRA] (OVIRT-2790) Jenkins: build manual trigger rights for asocha

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39787#comment-39787 ] Martin Perina commented on OVIRT-2790: -- {quote}Where did you find the instructions for using the manual

[JENKINS] Failed to setup proejct jenkins_gate

Failed to run project_setup.sh for: #91. 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]: 7aa8be7 (ovirt-ansible-cluster-upgrade) failed "ovirt-4.2" system tests

Change 7aa8be7 (ovirt-ansible-cluster-upgrade) 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

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

See Changes: [Barak Korren] slave-repos: Update mirror snapshots for EL7 [Barak Korren] Add Zuul jobs & project templates for gating [Barak Korren] automation: Drop Python 2