- Infra - oVirt List Archives

[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources
by jenkins＠jenkins.phx.ovirt.org 17 Sep '19

17 Sep '19

Failed to run project_setup.sh for: #359 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 openshift-integ-tests-container-15srs.

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources
by jenkins＠jenkins.phx.ovirt.org 17 Sep '19

17 Sep '19

Failed to run project_setup.sh for: #359 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 openshift-integ-tests-container-rspnq.

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources
by jenkins＠jenkins.phx.ovirt.org 17 Sep '19

17 Sep '19

Failed to run project_setup.sh for: #359 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 openshift-integ-tests-container-41rzj.

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources
by jenkins＠jenkins.phx.ovirt.org 17 Sep '19

17 Sep '19

Failed to run project_setup.sh for: #359 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 openshift-integ-tests-container-r8stj.

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources
by jenkins＠jenkins.phx.ovirt.org 17 Sep '19

17 Sep '19

Failed to run project_setup.sh for: #359 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 openshift-integ-tests-container-qnpvq.

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources
by jenkins＠jenkins.phx.ovirt.org 17 Sep '19

17 Sep '19

Failed to run project_setup.sh for: #359 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 openshift-integ-tests-container-m8rn7.

1 0

oVirt infra daily report - unstable production jobs - 950
by jenkins＠jenkins.phx.ovirt.org 17 Sep '19

17 Sep '19

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/950//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 103378, 1 (ovirt-engine-nodejs-modules) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 16 Sep '19

16 Sep '19

A system test invoked by the "ovirt-4.2" change queue including change 103378,1 (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 cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 102923,3 (ovirt-engine-nodejs- modules) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/103378/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/102923/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4805/

1 0

[JIRA] (OVIRT-2795) Re: [ovirt-devel] ovirt-vmconsole package issues
by Evgheni Dereveanchin (oVirt JIRA) 16 Sep '19

16 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2795?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-2795: ---------------------------------------- Status: In Progress (was: To Do) > Re: [ovirt-devel] ovirt-vmconsole package issues > ------------------------------------------------ > > Key: OVIRT-2795 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2795 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Nir Soffer > Assignee: Evgheni Dereveanchin > > On Wed, Sep 11, 2019 at 4:38 PM Michal Skrivanek < > michal.skrivanek(a)redhat.com> wrote: > > > > > > On 11 Sep 2019, at 11:19, Marcin Sobczyk <msobczyk(a)redhat.com> wrote: > > > > Hi, > > > > we get a lot of failures in the CI for el7 and fc29 regarding this package > > since this morning, i.e. for fc29: > > > > > > in which CI? > > > Here are some examples: > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > Adding infra-support to file a bug. > > > > > > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] [MIRROR] ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 38712 but expected size is: 38804 > > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] [MIRROR] ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 38712 but expected size is: 38804 > > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] [MIRROR] ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 38712 but expected size is: 38804 > > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] [MIRROR] ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 38712 but expected size is: 38804 > > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] [FAILED] ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: No more mirrors to try - All mirrors were already tried without success > > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] Error: Error downloading packages: > > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] Cannot download noarch/ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: All mirrors were tried > > > > Can someone take a look at this? > > > > as it looks like incomplete package or webserver issue it’s best to report > > this to infra > > > > Thanks, Marcin > > > > > > _______________________________________________ > > Infra mailing list -- infra(a)ovirt.org > > To unsubscribe send an email to infra-leave(a)ovirt.org > > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > > oVirt Code of Conduct: > > https://www.ovirt.org/community/about/community-guidelines/ > > List Archives: > > https://lists.ovirt.org/archives/list/infra@ovirt.org/message/GE3G2RZ3TPXHV… > > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100109)

1 0

[JIRA] (OVIRT-2795) Re: [ovirt-devel] ovirt-vmconsole package issues
by Evgheni Dereveanchin (oVirt JIRA) 16 Sep '19

16 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2795?page=com.atlassian.jira.… ] Evgheni Dereveanchin commented on OVIRT-2795: --------------------------------------------- The “Package does not match intended download“ typically means that the RPM was rebuilt without a version bump and the old one was already cached on the proxy. This means that metadata indicates one size while the cache contains a different RPM with a different size. This is exactly what I’ve seen in this case as well as the RPM called ovirt-vmconsole-1.0.7-3.el7.noarch.rpm was built on September 10: [https://jenkins.ovirt.org/job/ovirt-vmconsole_master_build-artifacts-el7-x8…] In squid logs however I see downloads of this same filename for at least a month before that. I’ve dropped squid cache for URLs http://resources.ovirt.org/repos/ovirt/tested/master/rpm/el7/noarch/ovirt-v… and [http://resources.ovirt.org/repos/ovirt/tested/master/rpm/fc29/noarch/ovirt-…] so everything should work fine now however this habit can backfire in other places as well so all RPMs should have unique version names after each rebuild to avoid such issues. [~accountid:557058:09f61156-7277-4b0a-b675-09e8e086f46a] FYI > Re: [ovirt-devel] ovirt-vmconsole package issues > ------------------------------------------------ > > Key: OVIRT-2795 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2795 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Nir Soffer > Assignee: Evgheni Dereveanchin > > On Wed, Sep 11, 2019 at 4:38 PM Michal Skrivanek < > michal.skrivanek(a)redhat.com> wrote: > > > > > > On 11 Sep 2019, at 11:19, Marcin Sobczyk <msobczyk(a)redhat.com> wrote: > > > > Hi, > > > > we get a lot of failures in the CI for el7 and fc29 regarding this package > > since this morning, i.e. for fc29: > > > > > > in which CI? > > > Here are some examples: > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > Adding infra-support to file a bug. > > > > > > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] [MIRROR] ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 38712 but expected size is: 38804 > > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] [MIRROR] ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 38712 but expected size is: 38804 > > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] [MIRROR] ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 38712 but expected size is: 38804 > > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] [MIRROR] ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 38712 but expected size is: 38804 > > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] [FAILED] ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: No more mirrors to try - All mirrors were already tried without success > > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] Error: Error downloading packages: > > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] Cannot download noarch/ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: All mirrors were tried > > > > Can someone take a look at this? > > > > as it looks like incomplete package or webserver issue it’s best to report > > this to infra > > > > Thanks, Marcin > > > > > > _______________________________________________ > > Infra mailing list -- infra(a)ovirt.org > > To unsubscribe send an email to infra-leave(a)ovirt.org > > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > > oVirt Code of Conduct: > > https://www.ovirt.org/community/about/community-guidelines/ > > List Archives: > > https://lists.ovirt.org/archives/list/infra@ovirt.org/message/GE3G2RZ3TPXHV… > > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100109)

1 0

[JIRA] (OVIRT-2795) Re: [ovirt-devel] ovirt-vmconsole package issues
by Evgheni Dereveanchin (oVirt JIRA) 16 Sep '19

16 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2795?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-2795: ---------------------------------------- Issue Type: Bug (was: By-EMAIL) > Re: [ovirt-devel] ovirt-vmconsole package issues > ------------------------------------------------ > > Key: OVIRT-2795 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2795 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Nir Soffer > Assignee: Evgheni Dereveanchin > > On Wed, Sep 11, 2019 at 4:38 PM Michal Skrivanek < > michal.skrivanek(a)redhat.com> wrote: > > > > > > On 11 Sep 2019, at 11:19, Marcin Sobczyk <msobczyk(a)redhat.com> wrote: > > > > Hi, > > > > we get a lot of failures in the CI for el7 and fc29 regarding this package > > since this morning, i.e. for fc29: > > > > > > in which CI? > > > Here are some examples: > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > Adding infra-support to file a bug. > > > > > > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] [MIRROR] ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 38712 but expected size is: 38804 > > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] [MIRROR] ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 38712 but expected size is: 38804 > > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] [MIRROR] ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 38712 but expected size is: 38804 > > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] [MIRROR] ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 38712 but expected size is: 38804 > > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] [FAILED] ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: No more mirrors to try - All mirrors were already tried without success > > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] Error: Error downloading packages: > > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] Cannot download noarch/ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: All mirrors were tried > > > > Can someone take a look at this? > > > > as it looks like incomplete package or webserver issue it’s best to report > > this to infra > > > > Thanks, Marcin > > > > > > _______________________________________________ > > Infra mailing list -- infra(a)ovirt.org > > To unsubscribe send an email to infra-leave(a)ovirt.org > > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > > oVirt Code of Conduct: > > https://www.ovirt.org/community/about/community-guidelines/ > > List Archives: > > https://lists.ovirt.org/archives/list/infra@ovirt.org/message/GE3G2RZ3TPXHV… > > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100109)

1 0

[CQ]: 98964, 22 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 16 Sep '19

16 Sep '19

A system test invoked by the "ovirt-master" change queue including change 98964,22 (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 failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 102717,6 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/98964/22 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/102717/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15862/

1 0

[JIRA] (OVIRT-2795) Re: [ovirt-devel] ovirt-vmconsole package issues
by Evgheni Dereveanchin (oVirt JIRA) 16 Sep '19

16 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2795?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2795: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Re: [ovirt-devel] ovirt-vmconsole package issues > ------------------------------------------------ > > Key: OVIRT-2795 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2795 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: Evgheni Dereveanchin > > On Wed, Sep 11, 2019 at 4:38 PM Michal Skrivanek < > michal.skrivanek(a)redhat.com> wrote: > > > > > > On 11 Sep 2019, at 11:19, Marcin Sobczyk <msobczyk(a)redhat.com> wrote: > > > > Hi, > > > > we get a lot of failures in the CI for el7 and fc29 regarding this package > > since this morning, i.e. for fc29: > > > > > > in which CI? > > > Here are some examples: > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > Adding infra-support to file a bug. > > > > > > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] [MIRROR] ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 38712 but expected size is: 38804 > > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] [MIRROR] ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 38712 but expected size is: 38804 > > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] [MIRROR] ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 38712 but expected size is: 38804 > > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] [MIRROR] ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 38712 but expected size is: 38804 > > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] [FAILED] ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: No more mirrors to try - All mirrors were already tried without success > > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] Error: Error downloading packages: > > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] Cannot download noarch/ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: All mirrors were tried > > > > Can someone take a look at this? > > > > as it looks like incomplete package or webserver issue it’s best to report > > this to infra > > > > Thanks, Marcin > > > > > > _______________________________________________ > > Infra mailing list -- infra(a)ovirt.org > > To unsubscribe send an email to infra-leave(a)ovirt.org > > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > > oVirt Code of Conduct: > > https://www.ovirt.org/community/about/community-guidelines/ > > List Archives: > > https://lists.ovirt.org/archives/list/infra@ovirt.org/message/GE3G2RZ3TPXHV… > > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100109)

1 0

[CQ]: 339a4a8 (ovirt-ansible-hosted-engine-setup) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 16 Sep '19

16 Sep '19

A system test invoked by the "ovirt-4.2" change queue including change 339a4a8 (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 detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 5a784af (ovirt-ansible-hosted- engine-setup) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/339a4a8bb… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/5a784af36… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4803/

1 0

[CQ]: 339a4a8 (ovirt-ansible-hosted-engine-setup) failed "ovirt-master" system tests
by oVirt Jenkins 16 Sep '19

16 Sep '19

Change 339a4a8 (ovirt-ansible-hosted-engine-setup) 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 change see: https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/339a4a8bb… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15860/

1 0

[JENKINS] Failed to setup proejct jenkins_gate
by jenkins＠jenkins.phx.ovirt.org 16 Sep '19

16 Sep '19

Failed to run project_setup.sh for: #104. 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-integ-tests-container-wm34m.

1 0

[JENKINS] Failed to setup proejct jenkins_gate
by jenkins＠jenkins.phx.ovirt.org 16 Sep '19

16 Sep '19

Failed to run project_setup.sh for: #100. 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-integ-tests-container-k1zj1.

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 16 Sep '19

16 Sep '19

Failed to run project_setup.sh for: #5500 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 openshift-integ-tests-container-3r9jr.

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 16 Sep '19

16 Sep '19

Failed to run project_setup.sh for: #5496 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 openshift-integ-tests-container-3wffd.

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 16 Sep '19

16 Sep '19

Failed to run project_setup.sh for: #5495 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 openshift-integ-tests-container-vxb4s.

1 0

[CQ]: 103262, 8 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 16 Sep '19

16 Sep '19

A system test invoked by the "ovirt-master" change queue including change 103262,8 (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 failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 102717,6 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/103262/8 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/102717/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15856/

1 0

[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 16 Sep '19

16 Sep '19

Failed to run project_setup.sh for: #633 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 openshift-integ-tests-container-jvdm0.

1 0

[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 16 Sep '19

16 Sep '19

Failed to run project_setup.sh for: #632 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 openshift-integ-tests-container-dbk8f.

1 0

[CQ]: 103171, 5 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 16 Sep '19

16 Sep '19

A system test invoked by the "ovirt-master" change queue including change 103171,5 (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 failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 102717,6 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/103171/5 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/102717/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15855/

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 16 Sep '19

16 Sep '19

Failed to run project_setup.sh for: #5494 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 openshift-integ-tests-container-3q2hz.

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 16 Sep '19

16 Sep '19

Failed to run project_setup.sh for: #5493 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 openshift-integ-tests-container-xswws.

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 16 Sep '19

16 Sep '19

Failed to run project_setup.sh for: #5492 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 openshift-integ-tests-container-z2qgq.

1 0

[JENKINS] Failed to setup proejct standard-manual-runner
by jenkins＠jenkins.phx.ovirt.org 16 Sep '19

16 Sep '19

Failed to run project_setup.sh for: #716 vdsm [check-network]. 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-integ-tests-container-fsmws.

1 2

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 16 Sep '19

16 Sep '19

Failed to run project_setup.sh for: #5491 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 openshift-integ-tests-container-s8h6l.

1 0

[JENKINS] Failed to setup proejct jenkins_gate
by jenkins＠jenkins.phx.ovirt.org 16 Sep '19

16 Sep '19

Failed to run project_setup.sh for: #98. 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-integ-tests-container-v21v8.

1 0

[JENKINS] Failed to setup proejct standard-manual-runner
by jenkins＠jenkins.phx.ovirt.org 16 Sep '19

16 Sep '19

Failed to run project_setup.sh for: #716 vdsm [check-network]. 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-integ-tests-container-kldpv.

1 0

[JENKINS] Failed to setup proejct vdsm_master_standard-poll-upstream-sources
by jenkins＠jenkins.phx.ovirt.org 16 Sep '19

16 Sep '19

Failed to run project_setup.sh for: #18 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 openshift-integ-tests-container-z5rk5.

1 0

[JENKINS] Failed to setup proejct vdsm_master_standard-poll-upstream-sources
by jenkins＠jenkins.phx.ovirt.org 16 Sep '19

16 Sep '19

Failed to run project_setup.sh for: #18 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 openshift-integ-tests-container-l3t78.

1 0

[JENKINS] Failed to setup proejct vdsm_master_standard-poll-upstream-sources
by jenkins＠jenkins.phx.ovirt.org 16 Sep '19

16 Sep '19

Failed to run project_setup.sh for: #18 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 openshift-integ-tests-container-59zxc.

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources
by jenkins＠jenkins.phx.ovirt.org 16 Sep '19

16 Sep '19

Failed to run project_setup.sh for: #358 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 openshift-integ-tests-container-zxqt1.

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources
by jenkins＠jenkins.phx.ovirt.org 16 Sep '19

16 Sep '19

Failed to run project_setup.sh for: #358 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 openshift-integ-tests-container-6k1r7.

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources
by jenkins＠jenkins.phx.ovirt.org 16 Sep '19

16 Sep '19

Failed to run project_setup.sh for: #358 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 openshift-integ-tests-container-jzbbq.

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources
by jenkins＠jenkins.phx.ovirt.org 16 Sep '19

16 Sep '19

Failed to run project_setup.sh for: #358 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 openshift-integ-tests-container-h8vgc.

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources
by jenkins＠jenkins.phx.ovirt.org 16 Sep '19

16 Sep '19

Failed to run project_setup.sh for: #358 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 openshift-integ-tests-container-pzg53.

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources
by jenkins＠jenkins.phx.ovirt.org 16 Sep '19

16 Sep '19

Failed to run project_setup.sh for: #358 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 openshift-integ-tests-container-svqc0.

1 0

[CQ]: 103212, 3 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 16 Sep '19

16 Sep '19

A system test invoked by the "ovirt-master" change queue including change 103212,3 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 103343,4 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 103343,4 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/103212/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/103343/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15852/

1 0

oVirt infra daily report - unstable production jobs - 949
by jenkins＠jenkins.phx.ovirt.org 16 Sep '19

16 Sep '19

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/949//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 103343,4 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 16 Sep '19

16 Sep '19

Change 103343,4 (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 change see: https://gerrit.ovirt.org/#/c/103343/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15851/

1 0

[JENKINS] Failed to setup proejct standard-manual-runner
by jenkins＠jenkins.phx.ovirt.org 15 Sep '19

15 Sep '19

Failed to run project_setup.sh for: #714 vdsm [check-network]. 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-integ-tests-container-ml7cq.

1 2

[CQ]: 103290, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 15 Sep '19

15 Sep '19

A system test invoked by the "ovirt-master" change queue including change 103290,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 failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 102717,6 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/103290/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/102717/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15848/

1 0

[CQ]: 103344,1 (ioprocess) failed "ovirt-4.3" system tests
by oVirt Jenkins 15 Sep '19

15 Sep '19

Change 103344,1 (ioprocess) 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 change see: https://gerrit.ovirt.org/#/c/103344/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2056/

1 0

[JENKINS] Failed to setup proejct standard-manual-runner
by jenkins＠jenkins.phx.ovirt.org 15 Sep '19

15 Sep '19

Failed to run project_setup.sh for: #714 vdsm [check-network]. 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-integ-tests-container-mv8x3.

1 0

[JENKINS] Failed to setup proejct standard-manual-runner
by jenkins＠jenkins.phx.ovirt.org 15 Sep '19

15 Sep '19

Failed to run project_setup.sh for: #714 vdsm [check-network]. 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-integ-tests-container-hr3r3.

1 0

[JENKINS] Failed to setup proejct standard-manual-runner
by jenkins＠jenkins.phx.ovirt.org 15 Sep '19

15 Sep '19

Failed to run project_setup.sh for: #713 vdsm [check-network]. 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-integ-tests-container-5tjrg.

1 0

[JENKINS] Failed to setup proejct standard-manual-runner
by jenkins＠jenkins.phx.ovirt.org 15 Sep '19

15 Sep '19

Failed to run project_setup.sh for: #713 vdsm [check-network]. 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-integ-tests-container-mrcdc.

1 0