November 2020 - Infra - Ovirt List Archives

[oVirt Jenkins] deploy-to-gated-ovirt-master - Build #581 - FAILURE!

by jenkins＠jenkins.phx.ovirt.org

Build: https://jenkins.ovirt.org/job/deploy-to-gated-ovirt-master/581/ Build Name: #581 Build Status: FAILURE Gerrit change: null - title: null - project: null - branch: null - author: null <null>

4 years

1
0
0 / 0

[CQ]: 111913, 4 (ovirt-system-tests) failed "ovirt-4.3" system tests, but isn't the failure root cause

by oVirt Jenkins

A system test invoked by the "ovirt-4.3" change queue including change 111913,4 (ovirt-system-tests) failed. However, this change seems not to be the root cause for this failure. Change 111946,2 (ovirt-system-tests) 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 111946,2 (ovirt-system-tests) 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/111913/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/111946/2 For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/4026/

4 years

1
0
0 / 0

[CQ]: 111913, 4 (ovirt-system-tests) 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 111913,4 (ovirt-system-tests) failed. However, this change seems not to be the root cause for this failure. Change 111946,2 (ovirt-system-tests) 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 111946,2 (ovirt-system-tests) 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/111913/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/111946/2 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/26733/

4 years

1
0
0 / 0

[oVirt Jenkins] deploy-to-gated-ovirt-4.3 - Build #584 - FAILURE!

by jenkins＠jenkins.phx.ovirt.org

Build: https://jenkins.ovirt.org/job/deploy-to-gated-ovirt-4.3/584/ Build Name: #584 Build Status: FAILURE Gerrit change: null - title: null - project: null - branch: null - author: null <null>

4 years

1
0
0 / 0

[JENKINS] Failed to setup proejct vdsm_standard-check-patch

by jenkins＠jenkins.phx.ovirt.org

Failed to run project_setup.sh for: #24751 vdsm [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 vm0144.workers-phx.ovirt.org.

4 years

1
0
0 / 0

[JENKINS] Failed to setup proejct vdsm_standard-check-patch

by jenkins＠jenkins.phx.ovirt.org

Failed to run project_setup.sh for: #24752 vdsm [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 vm0141.workers-phx.ovirt.org.

4 years

1
0
0 / 0

[JIRA] (OVIRT-3051) [FIRING:1] LowDiskSpace_NodeExporter_v1_0 resources.ovirt.org:9100 ovirt-resources (/dev/mapper/resources_lvm-data ext4 /srv/resources)

by Shlomi Zidmi (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3051?page=com.atlassian.jir... ] Shlomi Zidmi updated OVIRT-3051: -------------------------------- Resolution: Fixed Status: Done (was: To Do) This alert was fired before the cleanup occurred. Let's re-adjust the alert rule to wait for a longer period of time before firing the alert. > [FIRING:1] LowDiskSpace_NodeExporter_v1_0 resources.ovirt.org:9100 ovirt-resources (/dev/mapper/resources_lvm-data ext4 /srv/resources) > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-3051 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3051 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Alertmanager_Bot > Assignee: infra > Labels: ALERT{alertname="LowDiskSpace_NodeExporter_v1_0",instance="resources.ovirt.org:9100",job="ovirt-resources"} > > Labels: > - alertname = LowDiskSpace_NodeExporter_v1_0 > - device = /dev/mapper/resources_lvm-data > - fstype = ext4 > - instance = resources.ovirt.org:9100 > - job = ovirt-resources > - mountpoint = /srv/resources > Annotations: > - description = resources.ovirt.org:9100 of job ovirt-resources has less than 10% free disk space > Source: http://prometheus-0:9090/graph?g0.expr=node_filesystem_free_bytes+%2F+nod... -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100149)

4 years

1
0
0 / 0

[JENKINS] Failed to setup proejct vdsm_standard-check-patch

by jenkins＠jenkins.phx.ovirt.org

Failed to run project_setup.sh for: #24737 vdsm [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 vm0141.workers-phx.ovirt.org.

4 years

1
0
0 / 0

[JENKINS] Failed to setup proejct vdsm_standard-check-patch

by jenkins＠jenkins.phx.ovirt.org

Failed to run project_setup.sh for: #24733 vdsm [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 vm0144.workers-phx.ovirt.org.

4 years

1
0
0 / 0

[CQ]: 112002,1 (jenkins) failed "dummy-master" system tests

by oVirt Jenkins

Change 112002,1 (jenkins) is probably the reason behind recent system test failures in the "dummy-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/112002/1 For failed test results see: https://jenkins.ovirt.org/job/dummy-master_change-queue-tester/549/

4 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra November 2020