oVirt infra daily report - unstable production jobs - 754

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

[CQ]: b2ac05e (v2v-conversion-host) failed "ovirt-master" system tests

Change b2ac05e (v2v-conversion-host) 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 detail

[JIRA] (OVIRT-2566) make network suite blocking

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39119#comment-39119 ] Nir Soffer commented on OVIRT-2566: --- On Mon, Nov 5, 2018 at 8:59 AM danken (oVirt JIRA) <

Re: [JIRA] (OVIRT-2566) make network suite blocking

On Mon, Nov 5, 2018 at 8:59 AM danken (oVirt JIRA) < j...@ovirt-jira.atlassian.net> wrote: > danken created OVIRT-2566: > - > > Summary: make network suite blocking > Key: OVIRT-2566 > URL: https://ovirt-jira.atlassian.net/

[CQ]: ad74db5 (v2v-conversion-host) failed "ovirt-master" system tests

Change ad74db5 (v2v-conversion-host) 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 detail

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr

Failed to run project_setup.sh for: #1478 containerized-data-importer [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 op

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr

Failed to run project_setup.sh for: #1478 containerized-data-importer [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 op

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr

Failed to run project_setup.sh for: #1477 containerized-data-importer [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 op

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr

Failed to run project_setup.sh for: #1477 containerized-data-importer [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 op

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr

Failed to run project_setup.sh for: #1476 containerized-data-importer [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 op

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

Failed to run project_setup.sh for: #3686 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 openshift-kubevirt-or

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

Failed to run project_setup.sh for: #3686 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 openshift-kubevirt-or

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

Failed to run project_setup.sh for: #3686 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 openshift-kubevirt-or

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

Failed to run project_setup.sh for: #3686 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 openshift-kubevirt-or

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

Failed to run project_setup.sh for: #3685 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 openshift-kubevirt-or

[JIRA] (OVIRT-2693) [request] jenkins dev permission

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Marchukov reassigned OVIRT-2693: -- Assignee: Anton Marchukov (was: infra) > [request] jenkins dev permission >

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

Failed to run project_setup.sh for: #3685 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 openshift-kubevirt-or

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

Failed to run project_setup.sh for: #3685 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 openshift-kubevirt-or

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

Failed to run project_setup.sh for: #3685 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 openshift-kubevirt-or

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr

Failed to run project_setup.sh for: #1475 containerized-data-importer [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 op

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr

Failed to run project_setup.sh for: #1474 containerized-data-importer [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 op

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr

Failed to run project_setup.sh for: #1473 containerized-data-importer [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 op

Re: [JIRA] (OVIRT-2566) make network suite blocking

We still need to allocate bare metal to run it on each CQ run, and I'm not sure we have available resources for it, pretty sure we don't have since KubeVirt took half of the hosts. On Mon, Mar 4, 2019 at 2:09 PM danken (oVirt JIRA) < j...@ovirt-jira.atlassian.net> wrote: > > [ > https://ovir

[JIRA] (OVIRT-2566) make network suite blocking

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39115#comment-39115 ] Eyal Edri commented on OVIRT-2566: -- We still need to allocate bare metal to run it on each CQ

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

Failed to run project_setup.sh for: #3684 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 openshift-kubevirt-or

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

Failed to run project_setup.sh for: #3684 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 openshift-kubevirt-or

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

Failed to run project_setup.sh for: #3684 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 openshift-kubevirt-or

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

Failed to run project_setup.sh for: #3684 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 openshift-kubevirt-or

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

Failed to run project_setup.sh for: #3683 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 openshift-kubevirt-or

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

Failed to run project_setup.sh for: #3683 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 openshift-kubevirt-or

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

Failed to run project_setup.sh for: #3683 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 openshift-kubevirt-or

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

Failed to run project_setup.sh for: #3683 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 openshift-kubevirt-or

Jenkins build is back to stable : ovirt_master_publish-rpms_nightly #1278

See ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt

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

Failed to run project_setup.sh for: #3683 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 openshift-kubevirt-or

[JIRA] (OVIRT-2566) make network suite blocking

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39113#comment-39113 ] danken commented on OVIRT-2566: --- Is there news here? Would you try adding it? A benefit for seq

Jenkins build is back to stable : ovirt_4.2_publish-rpms_nightly #525

See ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Cod

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

Failed to run project_setup.sh for: #3683 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 openshift-kubevirt-or

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

Failed to run project_setup.sh for: #3682 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 openshift-kubevirt-or

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

Failed to run project_setup.sh for: #3682 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 openshift-kubevirt-or

[CQ]: f7c5585 (ovirt-ansible-engine-setup) failed "ovirt-4.2" system tests

Change f7c5585 (ovirt-ansible-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 de

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

Failed to run project_setup.sh for: #3682 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 openshift-kubevirt-or

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

Failed to run project_setup.sh for: #3682 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 openshift-kubevirt-or

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

Failed to run project_setup.sh for: #3682 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 openshift-kubevirt-or

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

Failed to run project_setup.sh for: #3681 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 openshift-kubevirt-or

Re: [CQ]: 98203, 1 (ovirt-engine-extension-aaa-jdbc) failed "ovirt-master" system tests

This was reported to the list and a bugzilla opened to fix it until the issue is resolved I will add a skiptest On Mon, Mar 4, 2019 at 9:42 AM oVirt Jenkins wrote: > Change 98203,1 (ovirt-engine-extension-aaa-jdbc) is probably the reason > behind > recent system test failures in the "ovirt-maste

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt Master (ovirt-engine-nodejs-modules) ] [ 27-02-2019 ] [ 002_bootstrap.add_vm2_lease ]

As I had another failure of this today I will be disabling this test until issue is resolved (https://bugzilla.redhat.com/1684267) Thanks, Dafna On Thu, Feb 28, 2019 at 8:48 PM Nir Soffer wrote: > On Thu, Feb 28, 2019 at 11:52 AM Dafna Ron wrote: > >> Hi, >> >> We have a failure on the projec

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

Failed to run project_setup.sh for: #3681 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 openshift-kubevirt-or

[JIRA] (OVIRT-2691) All builds on vm0145.workers-phx.ovirt.org (fc28 phx nested) fail with: Error fetching remote repo 'origin'

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39112#comment-39112 ] Barak Korren edited comment on OVIRT-2691 at 3/4/19 10:25 AM: -- Th

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

Failed to run project_setup.sh for: #3681 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 openshift-kubevirt-or

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

Failed to run project_setup.sh for: #3681 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 openshift-kubevirt-or

[CQ]: 98203, 1 (ovirt-engine-extension-aaa-jdbc) failed "ovirt-master" system tests

Change 98203,1 (ovirt-engine-extension-aaa-jdbc) 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 fu

[JIRA] (OVIRT-2691) All builds on vm0145.workers-phx.ovirt.org (fc28 phx nested) fail with: Error fetching remote repo 'origin'

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39112#comment-39112 ] Barak Korren commented on OVIRT-2691: - This is not a real clone failure - the issue is thi

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

Failed to run project_setup.sh for: #3680 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 openshift-kubevirt-or

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

Failed to run project_setup.sh for: #3680 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 openshift-kubevirt-or

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

Failed to run project_setup.sh for: #3680 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 openshift-kubevirt-or

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

Failed to run project_setup.sh for: #3680 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 openshift-kubevirt-or

[JIRA] (OVIRT-2693) [request] jenkins dev permission

Ahmad Khiet created OVIRT-2693: -- Summary: [request] jenkins dev permission Key: OVIRT-2693 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2693 Project: oVirt - virtualization made easy Issue

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

Failed to run project_setup.sh for: #3679 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 openshift-kubevirt-or

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

Failed to run project_setup.sh for: #3679 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 openshift-kubevirt-or

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

Failed to run project_setup.sh for: #3679 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 openshift-kubevirt-or

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

Failed to run project_setup.sh for: #3679 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 openshift-kubevirt-or

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

Failed to run project_setup.sh for: #3679 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 openshift-kubevirt-or

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

Failed to run project_setup.sh for: #3679 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 openshift-kubevirt-or

[JIRA] (OVIRT-2691) All builds on vm0145.workers-phx.ovirt.org (fc28 phx nested) fail with: Error fetching remote repo 'origin'

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39111#comment-39111 ] Anton Marchukov commented on OVIRT-2691: I have disabled this node for now till this i