- Infra - oVirt List Archives

[CQ]: 98495, 10 (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 98495,10 (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/98495/10 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/15844/

1 0

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

15 Sep '19

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

1 0

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

15 Sep '19

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

1 10

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

15 Sep '19

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

1 0

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

15 Sep '19

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

1 0

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

15 Sep '19

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

1 0

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

15 Sep '19

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

1 0

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

15 Sep '19

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

1 0

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

15 Sep '19

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

1 0

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

15 Sep '19

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

1 0

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

15 Sep '19

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

1 0

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

15 Sep '19

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

1 0

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

15 Sep '19

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

1 0

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

15 Sep '19

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

1 0

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

15 Sep '19

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

1 0

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

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

1 0

[oVirt] [CQ weekly status] [13-09-2019]
by Dusan Fodor 14 Sep '19

14 Sep '19

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.3*: GREEN (#3) No failure this week. *CQ-Master:* RED (#1) Last failure was on 12-09 was for ovirt-engine on adding storage domain. The issue is under investigation under thread "random failures for add_master_storage_domain". Current running jobs for 4.3 [1] and master [2] can be found here: [1] https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt -4.3_change-queue-tester/ [2] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt -master_change-queue-tester/ Have a nice week! Dusan ------------------------------------------------------------------------------------------------------------------- COLOUR MAP Green = job has been passing successfully ** green for more than 3 days may suggest we need a review of our test coverage 1. 1-3 days GREEN (#1) 2. 4-7 days GREEN (#2) 3. Over 7 days GREEN (#3) Yellow = intermittent failures for different projects but no lasting or current regressions ** intermittent would be a healthy project as we expect a number of failures during the week ** I will not report any of the solved failures or regressions. 1. Solved job failures YELLOW (#1) 2. Solved regressions YELLOW (#2) Red = job has been failing ** Active Failures. The colour will change based on the amount of time the project/s has been broken. Only active regressions would be reported. 1. 1-3 days RED (#1) 2. 4-7 days RED (#2) 3. Over 7 days RED (#3) _______________________________________________ Devel mailing list -- devel(a)ovirt.org To unsubscribe send an email to devel-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/devel@ovirt .org/message/YCNCKRK3G4EJXA3OCYAUS4VMKRDA67F4/

1 0

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

14 Sep '19

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

1 32

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

14 Sep '19

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

1 0

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

14 Sep '19

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

1 0

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

14 Sep '19

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

1 0

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

14 Sep '19

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

1 0

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

14 Sep '19

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

1 0

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

14 Sep '19

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

1 0

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

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

1 0

[CQ]: 103287,3 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 13 Sep '19

13 Sep '19

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

1 0

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

13 Sep '19

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

1 1

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

13 Sep '19

A system test invoked by the "ovirt-master" change queue including change 102956,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/102956/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/15836/

1 0

[JIRA] (OVIRT-2796) jenkins.ovirt.org unexpected restart
by Dusan Fodor (oVirt JIRA) 13 Sep '19

13 Sep '19

Dusan Fodor created OVIRT-2796: ---------------------------------- Summary: jenkins.ovirt.org unexpected restart Key: OVIRT-2796 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2796 Project: oVirt - virtualization made easy Issue Type: Outage Reporter: Dusan Fodor Assignee: infra ... at app. 13:45 CET, it is still restarting Could you please check why? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100109)

1 0

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

13 Sep '19

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

1 1

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

13 Sep '19

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

1 0

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

13 Sep '19

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

1 2

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

13 Sep '19

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

1 2

[CQ]: 103298, 1 (ovirt-host) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 13 Sep '19

13 Sep '19

A system test invoked by the "ovirt-master" change queue including change 103298,1 (ovirt-host) failed. However, this change seems not to be the root cause for this failure. Change 101396,1 (ovirt-host) 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 101396,1 (ovirt-host) 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/103298/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/101396/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15832/

1 0

[oVirt Jenkins] ovirt-system-tests_compat-4.3-suite-master - Build # 184 - Failure!
by jenkins＠jenkins.phx.ovirt.org 13 Sep '19

13 Sep '19

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.3-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.3-suite-master/184/ Build Number: 184 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #184 [jenkins CI] Auto create ovirt-master [Ehud Yonasi] Gate: run test suites. [Barak Korren] gate: Make suit types parameterized ----------------- Failed Tests: ----------------- No tests ran.

1 8

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

13 Sep '19

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

1 0

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

13 Sep '19

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

1 0

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

13 Sep '19

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

1 0

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

13 Sep '19

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

1 0

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

13 Sep '19

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

1 0

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

13 Sep '19

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

1 0

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

13 Sep '19

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

1 0

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

13 Sep '19

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

1 0

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

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

1 0

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

12 Sep '19

A system test invoked by the "ovirt-master" change queue including change 103291,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/103291/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/15830/

1 0

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

12 Sep '19

A system test invoked by the "ovirt-master" change queue including change 102834,6 (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/102834/6 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/15829/

1 0

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

12 Sep '19

A system test invoked by the "ovirt-master" change queue including change 103307,1 (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/103307/1 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/15827/

1 0

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

12 Sep '19

A system test invoked by the "ovirt-master" change queue including change 103208,3 (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/103208/3 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/15824/

1 0

[CQ]: 103294, 1 (ovirt-engine-api-model) failed "ovirt-master" system tests
by oVirt Jenkins 12 Sep '19

12 Sep '19

Change 103294,1 (ovirt-engine-api-model) 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/103294/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15821/

1 0

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

12 Sep '19

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

1 3