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

Failed to run project_setup.sh for: #591 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-2794) OST is broken since this morning - looks like infra issue

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-2794: Components: Jenkins Slaves > OST is broken since this morning - looks like infra issue >

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

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-2794: Labels: docker (was: ) > OST is broken since this morning - looks like infra issue >

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

Failed to run project_setup.sh for: #591 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-2794) OST is broken since this morning - looks like infra issue

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-2794: Description: The last successful build was today at 08:10: Since then all builds fail very early

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

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39798#comment-39798 ] Barak Korren commented on OVIRT-2794: - [~accountid:5aa0f39f5a4d022884128a0f] had started testing

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

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren reassigned OVIRT-2794: --- Assignee: Ehud Yonasi (was: infra) > OST is broken since this morning - looks like infra

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

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

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

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39797#comment-39797 ] Barak Korren commented on OVIRT-2794: - This was a bit Puzzling, we've seen issues between

[JENKINS] Failed to setup proejct standard-manual-runner

Failed to run project_setup.sh for: #695 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 standard-manual-runner

Failed to run project_setup.sh for: #695 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 standard-manual-runner

Failed to run project_setup.sh for: #695 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 standard-manual-runner

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

Re: [oVirt] [CQ weekly status] [07-09-2019]

Il giorno sab 7 set 2019 alle ore 15:49 Dusan Fodor ha scritto: > Hi, > > This mail is to provide the current status of CQ and allow people to > review status before and after the weekend. > Please refer to below colour map for further information on the meaning of > the colours. > > *CQ-4.2*:

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

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

[CQ]: 103112,5 (vdsm) failed "ovirt-master" system tests

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

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

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

Re: [oVirt] [CQ weekly status] [07-09-2019]

On Sat, Sep 7, 2019 at 4:49 PM Dusan Fodor wrote: > Hi, > > This mail is to provide the current status of CQ and allow people to > review status before and after the weekend. > Please refer to below colour map for further information on the meaning of > the colours. > > *CQ-4.2*: NOT RELEVANT >

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

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

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

[CQ]: 103185,3 (vdsm) failed "ovirt-master" system tests

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

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

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 nmstate_kubernetes-nmstate_standard-check-pr

Failed to run project_setup.sh for: #593 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: #594 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: #593 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: #594 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]: 103032,8 (vdsm) failed "ovirt-master" system tests

Change 103032,8 (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

[CQ]: 101057,5 (vdsm) failed "ovirt-master" system tests

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

[CQ]: 103200, 3 (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 103200,3 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 101057,5 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change

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

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

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

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

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

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

oVirt infra daily report - unstable production jobs - 943

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

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

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

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