September 2019 - Infra - Ovirt List Archives

[CQ]: 103180,3 (otopi) failed "ovirt-master" system tests

by oVirt Jenkins

Change 103180,3 (otopi) 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/103180/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15877/

5 years

1
0
0 / 0

[CQ]: 102989, 2 (ovirt-engine-api-explorer) failed "ovirt-4.2" system tests, but isn't the failure root cause

by oVirt Jenkins

A system test invoked by the "ovirt-4.2" change queue including change 102989,2 (ovirt-engine-api-explorer) failed. However, this change seems not to be the root cause for this failure. Change 103253,1 (ovirt-engine-api-explorer) 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 103253,1 (ovirt-engine-api- explorer) 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/102989/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/103253/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4809/

5 years

1
0
0 / 0

[CQ]: 103389,2 (vdsm) failed "ovirt-master" system tests

by oVirt Jenkins

Change 103389,2 (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/103389/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15875/

5 years

1
0
0 / 0

[JIRA] (OVIRT-2796) jenkins.ovirt.org unexpected restart

by Evgheni Dereveanchin (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2796?page=com.atlassian.jir... ] Evgheni Dereveanchin reassigned OVIRT-2796: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > 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: Evgheni Dereveanchin > > ... 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)

5 years

1
0
0 / 0

[CQ]: 103326, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

by oVirt Jenkins

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

5 years

1
0
0 / 0

[CQ]: 3db2098 (v2v-conversion-host) failed "ovirt-4.2" system tests, but isn't the failure root cause

by oVirt Jenkins

A system test invoked by the "ovirt-4.2" change queue including change 3db2098 (v2v-conversion-host) failed. However, this change seems not to be the root cause for this failure. Change 7acb519 (v2v-conversion-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 7acb519 (v2v-conversion-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://github.com/oVirt/v2v-conversion-host/commit/3db20988c6f0f2ec55c00... For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/v2v-conversion-host/commit/7acb519c2ffbcde17c8b5... For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4807/

5 years

1
0
0 / 0

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

by jenkins＠jenkins.phx.ovirt.org

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

5 years

1
0
0 / 0

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

by jenkins＠jenkins.phx.ovirt.org

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

5 years

1
0
0 / 0

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

by jenkins＠jenkins.phx.ovirt.org

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

5 years

1
0
0 / 0

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

by jenkins＠jenkins.phx.ovirt.org

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

5 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra September 2019