[CQ]: f619e0e (ovirt-ansible-hosted-engine-setup) 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 f619e0e (ovirt-ansible-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 5a784af (ovirt-ansible-hosted- engine-setup) that this change depends on or is based on, was

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

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

[oVirt Jenkins] ovirt-system-tests_compat-4.3-suite-master - Build # 184 - Failure!

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

[CQ]: 103020,4 (ovirt-provider-ovn) failed "ovirt-4.3" system tests

Change 103020,4 (ovirt-provider-ovn) 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

oVirt infra daily report - unstable production jobs - 938

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

[CQ]: 5a784af (ovirt-ansible-hosted-engine-setup) failed "ovirt-4.3" system tests

Change 5a784af (ovirt-ansible-hosted-engine-setup) 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

[CQ]: 102743,6 (ioprocess) failed "ovirt-master" system tests

Change 102743,6 (ioprocess) 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

[JENKINS] Failed to setup proejct jenkins_gate

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

See Changes: [Ehud Yonasi] Gate: run test suites. [Barak Korren] gate: Make suit types parameterized -- Started by timer Running as

[JENKINS] Failed to setup proejct jenkins_gate

Failed to run project_setup.sh for: #83. 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: #79. 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: #77. 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: #74. 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: #71. 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: #68. 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: #65. 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: #60. 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: #59. 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: #56. 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: #53. 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: #48. 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: #47. 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]: 102906, 6 (ovirt-engine-nodejs-modules) 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 102906,6 (ovirt-engine-nodejs-modules) failed. However, this change seems not to be the root cause for this failure. Change 102923,3 (ovirt-engine-nodejs-modules) that this change depends on or is based on, was detected as the

[JENKINS] Failed to setup proejct jenkins_gate

Failed to run project_setup.sh for: #44. 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: #41. 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: #38. 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]: 103041, 8 (ovirt-engine-ui-extensions) 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 103041,8 (ovirt-engine-ui-extensions) failed. However, this change seems not to be the root cause for this failure. Change 103040,1 (ovirt-engine-ui-extensions) that this change depends on or is based on, was detected as the

[JENKINS] Failed to setup proejct jenkins_gate

Failed to run project_setup.sh for: #35. 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-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=39786#comment-39786 ] Eyal Edri commented on OVIRT-2788: -- [~accountid:557058:c4a3432b-f1c1-4620-b53b-c398d6d3a5c2]

[JIRA] (OVIRT-2789) Fwd: Any chance you can remove dp...@redhat.com from infra@ovirt.org ?

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eyal Edri updated OVIRT-2789: - Resolution: Fixed Status: Done (was: To Do) > Fwd: Any chance you can remove dp...@redhat.com

[JIRA] (OVIRT-2789) Fwd: Any chance you can remove dp...@redhat.com from infra@ovirt.org ?

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39785#comment-39785 ] Eyal Edri edited comment on OVIRT-2789 at 9/4/19 3:21 PM: -- Done. removed him from

[JIRA] (OVIRT-2789) Fwd: Any chance you can remove dp...@redhat.com from infra@ovirt.org ?

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39785#comment-39785 ] Eyal Edri commented on OVIRT-2789: -- Done. removed him from infra list via the admin interface on

[JENKINS] Failed to setup proejct jenkins_gate

Failed to run project_setup.sh for: #32. 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: #29. 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]: d1d35ca (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 d1d35ca (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.

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

[CQ]: 103040, 1 (ovirt-engine-ui-extensions) failed "ovirt-4.3" system tests

Change 103040,1 (ovirt-engine-ui-extensions) 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

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

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

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

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