November 2018 - Infra - Ovirt List Archives

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

6 years, 5 months

1
0
0 / 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

by jenkins＠jenkins.phx.ovirt.org

Failed to run project_setup.sh for: #2414 kubevirt [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 ovirt-srv06.infra-phx.ovirt.org-container-1.

6 years, 5 months

1
0
0 / 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

by jenkins＠jenkins.phx.ovirt.org

Failed to run project_setup.sh for: #2413 kubevirt [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 ovirt-srv05.phx.ovirt.org-container-6.

6 years, 5 months

1
0
0 / 0

Jenkins – running ovirt-vmconsole builds

by Tomasz Barański

Hello, I'm trying to diagnose a failing build[1] in ovirt-vmconsole. It builds fine in a Fedora VM on my laptop, but fails on the Jenkins server. Is there a way to trigger the build with changes from a specific Gerrit changeset? Or maybe I can get permissions to run the build manually? Tomo [1] https://gerrit.ovirt.org/#/c/95175/

6 years, 5 months

3
3
0 / 0

[JIRA] (OVIRT-2569) attach bare metal node to OpenShift

by Daniel Belenky (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2569?page=com.atlassian.jir... ] Daniel Belenky reassigned OVIRT-2569: ------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > attach bare metal node to OpenShift > ----------------------------------- > > Key: OVIRT-2569 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2569 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: Evgheni Dereveanchin > Priority: High > > We want to use ephemeral openshift pods as Jenkins slaves and to be able to test virtualization capabilities we need to make sure we have a bare metal node for those pods. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

6 years, 5 months

1
0
0 / 0

[JIRA] (OVIRT-2569) attach bare metal node to OpenShift

by Daniel Belenky (oVirt JIRA)

Daniel Belenky created OVIRT-2569: ------------------------------------- Summary: attach bare metal node to OpenShift Key: OVIRT-2569 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2569 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Daniel Belenky Assignee: infra Priority: High We want to use ephemeral openshift pods as Jenkins slaves and to be able to test virtualization capabilities we need to make sure we have a bare metal node for those pods. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

6 years, 5 months

1
0
0 / 0

[JIRA] (OVIRT-2569) attach bare metal node to OpenShift

by Daniel Belenky (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2569?page=com.atlassian.jir... ] Daniel Belenky updated OVIRT-2569: ---------------------------------- Epic Link: OVIRT-403 > attach bare metal node to OpenShift > ----------------------------------- > > Key: OVIRT-2569 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2569 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > Priority: High > > We want to use ephemeral openshift pods as Jenkins slaves and to be able to test virtualization capabilities we need to make sure we have a bare metal node for those pods. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

6 years, 5 months

1
0
0 / 0

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

6 years, 5 months

1
0
0 / 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 628 - Failure!

by jenkins＠jenkins.phx.ovirt.org

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/628/ Build Number: 628 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #628 [Martin Perina] Fix notifier check in master and 4.2 ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.add_hosts Error Message: Host lago-hc-basic-suite-4-2-host1 is in non operational state -------------------- >> begin captured logging << -------------------- ovirtlago.testlib: ERROR: * Unhandled exception in <function _host_is_up_4 at 0x7fbda2568578> Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/002_bootstrap.py", line 259, in _host_is_up_4 raise RuntimeError('Host %s is in non operational state' % api_host.name) RuntimeError: Host lago-hc-basic-suite-4-2-host1 is in non operational state --------------------- >> end captured logging << --------------------- Stack Trace: File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/002_bootstrap.py", line 229, in add_hosts add_hosts_4(prefix) File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/002_bootstrap.py", line 273, in add_hosts_4 testlib.assert_true_within(_host_is_up_4, timeout=15*60) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 278, in assert_true_within assert_equals_within(func, True, timeout, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/002_bootstrap.py", line 259, in _host_is_up_4 raise RuntimeError('Host %s is in non operational state' % api_host.name) 'Host lago-hc-basic-suite-4-2-host1 is in non operational state\n-------------------- >> begin captured logging << --------------------\novirtlago.testlib: ERROR: * Unhandled exception in <function _host_is_up_4 at 0x7fbda2568578>\nTraceback (most recent call last):\n File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within\n res = func()\n File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/002_bootstrap.py", line 259, in _host_is_up_4\n raise RuntimeError(\'Host %s is in non operational state\' % api_host.name)\nRuntimeError: Host lago-hc-basic-suite-4-2-host1 is in non operational state\n--------------------- >> end captured logging << ---------------------'

6 years, 5 months

1
1
0 / 0

[CQ]: 95221, 2 (ovirt-engine-metrics) failed "ovirt-master" system tests

by oVirt Jenkins

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

6 years, 5 months

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra November 2018