November 2018 - Infra - Ovirt List Archives

[oVirt Jenkins] ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 - Build # 1 - Failure!

by jenkins＠jenkins.phx.ovirt.org

Project: http://jenkins.ovirt.org/job/ovirt-node-ng-image_4.3_build-artifacts-fc28... Build: http://jenkins.ovirt.org/job/ovirt-node-ng-image_4.3_build-artifacts-fc28... Build Number: 1 Build Status: Failure Triggered By: Started by user Sandro Bonazzola ------------------------------------- Changes Since Last Success: ------------------------------------- ----------------- Failed Tests: ----------------- No tests ran.

6 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-2556) kubevirt test runs and nested docker issue

by Roman Mohr (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2556?page=com.atlassian.jir... ] Roman Mohr updated OVIRT-2556: ------------------------------ Resolution: Fixed Status: Done (was: To Do) > kubevirt test runs and nested docker issue > ------------------------------------------ > > Key: OVIRT-2556 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2556 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Roman Mohr > Assignee: infra > > Hi, > we see a lot of tests which fail with during the setup [1] : > ``` > /usr/bin/docker-current: Error response from daemon: grpc: the > connection is unavailable. > time="2018-10-23T07:17:55Z" level=error msg="error getting events from > daemon: context canceled" > ``` > It looks like the docker daemon may not run properly. > Best Regards, > Roman > [1] https://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/2344//a... -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

6 years, 4 months

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: #164 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 vm0010.workers-phx.ovirt.org.

6 years, 4 months

1
0
0 / 0

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

6 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-2594) Build fail with "# /usr/sbin/groupadd -g 1000 mock" - no test was run

by Nir Soffer (oVirt JIRA)

Nir Soffer created OVIRT-2594: --------------------------------- Summary: Build fail with "# /usr/sbin/groupadd -g 1000 mock" - no test was run Key: OVIRT-2594 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2594 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra I have seen this issue in the recent days several times. Here are some examples: - https://jenkins.ovirt.org/job/vdsm_master_check-patch-fc28-x86_64/2269/co... - https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26243/co... - https://jenkins.ovirt.org/job/vdsm_standard-check-patch/91/console - https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26187/co... There are too issues: - No test ran, so we need to retrigger manually - Gerrit report build FAILURE instead of build ERROR I reported the second issue many times in the last 5 years, no progress yet. Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

6 years, 4 months

1
0
0 / 0

Build fail with "# /usr/sbin/groupadd -g 1000 mock" - no test was run

by Nir Soffer

I have seen this issue in the recent days several times. Here are some examples: - https://jenkins.ovirt.org/job/vdsm_master_check-patch-fc28-x86_64/2269/co... - https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26243/co... - https://jenkins.ovirt.org/job/vdsm_standard-check-patch/91/console - https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26187/co... There are too issues: - No test ran, so we need to retrigger manually - Gerrit report build FAILURE instead of build ERROR I reported the second issue many times in the last 5 years, no progress yet. Nir

6 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-2589) CI random failures on VDSM check-patch

by Eyal Edri (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2589?page=com.atlassian.jir... ] Eyal Edri reassigned OVIRT-2589: -------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > CI random failures on VDSM check-patch > -------------------------------------- > > Key: OVIRT-2589 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2589 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Edward Haas > Assignee: Evgheni Dereveanchin > > Hello, > It seems we are experiencing random failures on the CI VDSM check-patch, > Could you please have a look? > https://jenkins.ovirt.org/job/vdsm_standard-check-patch/108/ > https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26203/ > Some have errors of improper imports, as if the slave is not "clean". > Thanks, > Edy. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

6 years, 4 months

1
0
0 / 0

[CQ]: 95686, 2 (ovirt-engine) 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 95686,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 95525,2 (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 95525,2 (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/95686/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/95525/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3538/

6 years, 4 months

1
0
0 / 0

[CQ]: 95685, 2 (ovirt-engine) 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 95685,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 95525,2 (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 95525,2 (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/95685/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/95525/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3537/

6 years, 4 months

1
0
0 / 0

[CQ]: 95681, 1 (ovirt-engine-extension-logger-log4j) 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 95681,1 (ovirt-engine-extension-logger-log4j) failed. However, this change seems not to be the root cause for this failure. Change 95680,1 (ovirt-engine- extension-logger-log4j) 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 95680,1 (ovirt-engine- extension-logger-log4j) 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/95681/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/95680/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11643/

6 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra November 2018