- Infra - oVirt List Archives

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

05 Sep '19

Failed to run project_setup.sh for: #5432 ovirt-system-tests [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-integ-tests-container-gw86w.

1 0

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

05 Sep '19

Failed to run project_setup.sh for: #5432 ovirt-system-tests [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-integ-tests-container-k0d9w.

1 0

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

05 Sep '19

Failed to run project_setup.sh for: #5432 ovirt-system-tests [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-integ-tests-container-tflwf.

1 0

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

05 Sep '19

Failed to run project_setup.sh for: #5432 ovirt-system-tests [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-integ-tests-container-bv9x8.

1 0

[CQ]: 5665964 (ovirt-ansible-vm-infra) failed "ovirt-4.2" system tests
by oVirt Jenkins 05 Sep '19

05 Sep '19

Change 5665964 (ovirt-ansible-vm-infra) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://github.com/oVirt/ovirt-ansible-vm-infra/commit/5665964164d485f4aa38… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4782/

1 0

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

05 Sep '19

Failed to run project_setup.sh for: #5432 ovirt-system-tests [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-integ-tests-container-ssjwt.

1 0

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

05 Sep '19

Failed to run project_setup.sh for: #5432 ovirt-system-tests [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-integ-tests-container-wnv77.

1 0

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

05 Sep '19

Failed to run project_setup.sh for: #5431 ovirt-system-tests [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-integ-tests-container-jp1h6.

1 0

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

05 Sep '19

Failed to run project_setup.sh for: #5431 ovirt-system-tests [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-integ-tests-container-f698k.

1 0

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

05 Sep '19

Failed to run project_setup.sh for: #5431 ovirt-system-tests [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-integ-tests-container-02z34.

1 0

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

05 Sep '19

Failed to run project_setup.sh for: #5431 ovirt-system-tests [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-integ-tests-container-v0lfm.

1 0

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

05 Sep '19

Failed to run project_setup.sh for: #5431 ovirt-system-tests [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-integ-tests-container-4xdhw.

1 0

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

05 Sep '19

Failed to run project_setup.sh for: #5431 ovirt-system-tests [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-integ-tests-container-6pjfx.

1 0

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

05 Sep '19

Failed to run project_setup.sh for: #5431 ovirt-system-tests [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-integ-tests-container-p1jc3.

1 0

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

05 Sep '19

Failed to run project_setup.sh for: #5431 ovirt-system-tests [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-integ-tests-container-951vx.

1 0

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

05 Sep '19

Failed to run project_setup.sh for: #5431 ovirt-system-tests [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-integ-tests-container-r2p8m.

1 0

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

05 Sep '19

Failed to run project_setup.sh for: #5431 ovirt-system-tests [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-integ-tests-container-xvx47.

1 0

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

05 Sep '19

Failed to run project_setup.sh for: #5431 ovirt-system-tests [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-integ-tests-container-pqtmr.

1 0

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

05 Sep '19

Failed to run project_setup.sh for: #5431 ovirt-system-tests [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-integ-tests-container-9qm4b.

1 0

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

05 Sep '19

Failed to run project_setup.sh for: #5431 ovirt-system-tests [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-integ-tests-container-drddf.

1 0

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

05 Sep '19

A system test invoked by the "ovirt-4.3" change queue including change 103030,4 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 103020,4 (ovirt-provider-ovn) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 103020,4 (ovirt-provider-ovn) 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/103030/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/103020/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2009/

1 0

[JIRA] (OVIRT-2791) mirrors.phx returns 404 when accessing metadata
by Ehud Yonasi (oVirt JIRA) 05 Sep '19

05 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2791?page=com.atlassian.jira.… ] Ehud Yonasi commented on OVIRT-2791: ------------------------------------ Patch \[1] was merged today, try re-running the manual job again. \[1]: [https://gerrit.ovirt.org/#/c/103118/|https://gerrit.ovirt.org/#/c/103118/] > mirrors.phx returns 404 when accessing metadata > ----------------------------------------------- > > Key: OVIRT-2791 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2791 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dusan Fodor > Assignee: infra > > http://mirrors.phx.ovirt.org/repos/yum/epel-el7/2019-05-09-04-45/repodata/5…: [Errno 14] HTTP Error 404 - Not Found > Job example that failed on this: > http://jenkins.ovirt.org/job/ovirt-system-tests_manual/5532/console -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100109)

1 0

[JIRA] (OVIRT-2791) mirrors.phx returns 404 when accessing metadata
by Dusan Fodor (oVirt JIRA) 05 Sep '19

05 Sep '19

Dusan Fodor created OVIRT-2791: ---------------------------------- Summary: mirrors.phx returns 404 when accessing metadata Key: OVIRT-2791 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2791 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dusan Fodor Assignee: infra http://mirrors.phx.ovirt.org/repos/yum/epel-el7/2019-05-09-04-45/repodata/5…: [Errno 14] HTTP Error 404 - Not Found Job example that failed on this: http://jenkins.ovirt.org/job/ovirt-system-tests_manual/5532/console -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100109)

1 0

`jenkins` project is now gated
by Barak Korren 05 Sep '19

05 Sep '19

Hi everyone, Since we merged one of the more significant patches <https://gerrit.ovirt.org/c/102053/> for enabling patch gating yesterday, the `jenkins` repository is using the gating system as a showcase for this functionality. What this means in practice is that patches should no longer be merged manually to this repo. Instead, once the code review flag is set to +2 in Gerrit, and if the 'verified' and 'ci' flags are set to +1 as well, the gating job will be triggered, and if successful the patch will be merged automatically. The gating job for the `jenkins` repo does not run OST. Instead, it runs the `dummy_suit_master.sh` script that is stored in the repo itself. this script doesn't do much ATM. Regards, Barak. -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

1 0

[JIRA] (OVIRT-2788) CI: Add the option to send and email if stage fails
by Barak Korren (oVirt JIRA) 05 Sep '19

05 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2788?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2788: ------------------------------------- its not something you can define ATM. [~accountid:557058:c4a3432b-f1c1-4620-b53b-c398d6d3a5c2] started implementing this when we were working on the general notifications mechanism (That was mean to be used for the tag stages as well) for STDCI but he moved to work on other things. > CI: Add the option to send and email if stage fails > --------------------------------------------------- > > Key: OVIRT-2788 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2788 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: CI client projects > Reporter: Bell Levin > Assignee: infra > > Added the poll-upstream-sources stage to be ran every night on vdsm \[1]. I think it is useful if an email is sent to selected people if the stage has failed. > Such option is available in V1 (namely, the nightly ost network suite), and would help me out if implemented in V2 as well. > \[1] [https://gerrit.ovirt.org/#/c/102901/|https://gerrit.ovirt.org/#/c/102901/] > FYI [~accountid:557058:866c109f-3951-4680-8dac-b76caf296501] [~accountid:557058:c4a3432b-f1c1-4620-b53b-c398d6d3a5c2] [~accountid:5aa0f39f5a4d022884128a0f] -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100109)

1 0

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

05 Sep '19

Failed to run project_setup.sh for: #91. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-integ-tests-container-hmszw.

1 0

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

05 Sep '19

Failed to run project_setup.sh for: #89. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-integ-tests-container-v0d0n.

1 0

[JIRA] (OVIRT-2790) Jenkins: build manual trigger rights for asocha
by Barak Korren (oVirt JIRA) 05 Sep '19

05 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2790?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2790: ------------------------------------- [~accountid:557058:7013bb8c-48b2-4b9b-898e-eccf5fb61fad] {{ci test please}} had been around for a long long time - while triggering from the GUI is still usable, and not going to be removed any time soon, I personally prefer if people stay away from the jenkins GUI unless they are reading the logs. > Jenkins: build manual trigger rights for asocha > -------------------------------------------------- > > Key: OVIRT-2790 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2790 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins Master > Reporter: Artur Socha > Assignee: infra > Priority: Low > > Please grant me (jenkins user id: asocha) rights to manually trigger patch builds (to be able to re-run) > [https://jenkins.ovirt.org/gerrit_manual_trigger/|https://jenkins.ovirt.org/…] > Thanks\! -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100109)

1 0

[JIRA] (OVIRT-2790) Jenkins: build manual trigger rights for asocha
by Martin Perina (oVirt JIRA) 05 Sep '19

05 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2790?page=com.atlassian.jira.… ] Martin Perina commented on OVIRT-2790: -------------------------------------- {quote}Where did you find the instructions for using the manual trigger? we might need to update it?{quote} I haven’t seen any announcement about manual trigger being deprecate nor announcement about “ci test please”. Did I miss something? [~accountid:557058:5fc78873-359e-47c9-aa0b-4845b0da8143] > Jenkins: build manual trigger rights for asocha > -------------------------------------------------- > > Key: OVIRT-2790 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2790 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins Master > Reporter: Artur Socha > Assignee: infra > Priority: Low > > Please grant me (jenkins user id: asocha) rights to manually trigger patch builds (to be able to re-run) > [https://jenkins.ovirt.org/gerrit_manual_trigger/|https://jenkins.ovirt.org/…] > Thanks\! -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100109)

1 0

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

05 Sep '19

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 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/f619e0e8d… 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.3_change-queue-tester/2004/

1 0

[CQ]: 103020,4 (ovirt-provider-ovn) failed "ovirt-4.3" system tests
by oVirt Jenkins 05 Sep '19

05 Sep '19

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 about the change see: https://gerrit.ovirt.org/#/c/103020/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1999/

1 0

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

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

1 0

[CQ]: 5a784af (ovirt-ansible-hosted-engine-setup) failed "ovirt-4.3" system tests
by oVirt Jenkins 04 Sep '19

04 Sep '19

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 further details about the change see: https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/5a784af36… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1994/

1 0

[CQ]: 102743,6 (ioprocess) failed "ovirt-master" system tests
by oVirt Jenkins 04 Sep '19

04 Sep '19

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 the change see: https://gerrit.ovirt.org/#/c/102743/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15722/

1 0

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

04 Sep '19

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 openshift-integ-tests-container-qtbmg.

1 0

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

04 Sep '19

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 openshift-integ-tests-container-xjz9n.

1 0

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

04 Sep '19

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 openshift-integ-tests-container-0x6p5.

1 0

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

04 Sep '19

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 openshift-integ-tests-container-mr159.

1 0

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

04 Sep '19

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 openshift-integ-tests-container-tmrsw.

1 0

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

04 Sep '19

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 openshift-integ-tests-container-31z77.

1 0

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

04 Sep '19

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 openshift-integ-tests-container-r4jwc.

1 0

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

04 Sep '19

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 openshift-integ-tests-container-01p32.

1 0

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

04 Sep '19

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 openshift-integ-tests-container-7wct8.

1 0

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

04 Sep '19

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 openshift-integ-tests-container-dbl55.

1 0

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

04 Sep '19

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 openshift-integ-tests-container-l4mm1.

1 0

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

04 Sep '19

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 openshift-integ-tests-container-n6hw9.

1 0

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

04 Sep '19

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 openshift-integ-tests-container-bf01m.

1 0

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

04 Sep '19

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 openshift-integ-tests-container-4h7lx.

1 0

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

04 Sep '19

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 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/102906/6 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/4780/

1 0

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

04 Sep '19

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 openshift-integ-tests-container-fzxnh.

1 0