September 2018 - Infra - Ovirt List Archives

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

6 years, 1 month

1
0
0 / 0

[oVirt Jenkins] ovirt-system-tests_he-basic-ansible-suite-master - Build # 604 - Failure!

by jenkins＠jenkins.phx.ovirt.org

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-ma... Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-ma... Build Number: 604 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #604 [Gal Ben Haim] Adding dr suite [Barak Korren] Remove the populate_mock function from mock_runner [Daniel Belenky] mock_runner: store shell cmd in a variable [Barak Korren] mock_runner: Added timeout param [Barak Korren] Make whitelist repo configurable via env vars [Daniel Belenky] stdci_runner: let mock_runner manage timeout [Greg Sheremeta] remove 4.1 change queue from ovirt-engine-nodejs config ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 012_local_maintenance_sdk.local_maintenance Error Message: False != True after 600 seconds -------------------- >> begin captured logging << -------------------- root: INFO: * Waiting For System Stability... root: INFO: * Performing Deactivation... --------------------- >> 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 "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 79, in wrapper prefix.virt_env.engine_vm().get_api(api_ver=4), *args, **kwargs 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_he-basic-ansible-suite-master/ovirt-system-tests/he-basic-ansible-suite-master/test-scenarios/012_local_maintenance_sdk.py", line 65, in local_maintenance lambda: host_service.get().status == types.HostStatus.MAINTENANCE or File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 286, in assert_true_within_long assert_equals_within_long(func, True, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 273, in assert_equals_within_long func, value, LONG_TIMEOUT, allowed_exceptions=allowed_exceptions File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 252, in assert_equals_within '%s != %s after %s seconds' % (res, value, timeout) 'False != True after 600 seconds\n-------------------- >> begin captured logging << --------------------\nroot: INFO: * Waiting For System Stability...\nroot: INFO: * Performing Deactivation...\n--------------------- >> end captured logging << ---------------------'

6 years, 1 month

2
22
0 / 0

oVirt infra daily report - unstable production jobs - 581

by jenkins＠jenkins.phx.ovirt.org

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/581//artifact/exported... Cheers, Jenkins

6 years, 1 month

1
0
0 / 0

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

6 years, 1 month

1
0
0 / 0

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

6 years, 1 month

1
0
0 / 0

[JIRA] (OVIRT-2489) Add nmstate project to STDCI

by Edward Haas (oVirt JIRA)

Edward Haas created OVIRT-2489: ---------------------------------- Summary: Add nmstate project to STDCI Key: OVIRT-2489 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2489 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Edward Haas Assignee: infra Hello, nmstate is a new project that is aimed to replace most of the VDSM networking implementation and hopefully used to manage k8s nodes networking. It has raised from a joint effort between the NetworkManager team and oVirt networking team. We would like to utilize STDCI to run integration tests. A PR has been opened for this: https://github.com/nmstate/nmstate/pull/76 Could you please help us add it to the CI? Thanks, Edy. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100091)

6 years, 1 month

1
0
0 / 0

[CQ]: 93775,3 (vdsm) failed "ovirt-master" system tests

by oVirt Jenkins

Change 93775,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/93775/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10238/

6 years, 1 month

1
0
0 / 0

[JIRA] (OVIRT-2488) mirrors.phx running out of disk space

by Ehud Yonasi (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2488?page=com.atlassian.jir... ] Ehud Yonasi commented on OVIRT-2488: ------------------------------------ Yea. i understand there is no retention policy in place. Let's discuss about how far we want to keep backwards because as i see your growth report it's like 10 gigs weekly.. > mirrors.phx running out of disk space > ------------------------------------- > > Key: OVIRT-2488 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2488 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: infra > > mirrors.phx.ovirt.org is slowly running out of space. We should document the cleanup procedure so opening a tracker ticket. > Free disk space has dropped from 10% (61GB free) to 8.5% (52GB free) within the last week so we still have time to react. We can also modify alert thresholds or disable alerts if they're causing too much noise. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100091)

6 years, 1 month

1
0
0 / 0

[JIRA] (OVIRT-2488) mirrors.phx running out of disk space

by Evgheni Dereveanchin (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2488?page=com.atlassian.jir... ] Evgheni Dereveanchin commented on OVIRT-2488: --------------------------------------------- AFAIR there is no retention here as well. The disk filled up several times before and [~bkorren(a)redhat.com] performed manual cleanups. Now we have monitoring in place to know this in advance before mirros sync jobs start failing and also we can see the trend from the graphs. > mirrors.phx running out of disk space > ------------------------------------- > > Key: OVIRT-2488 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2488 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: infra > > mirrors.phx.ovirt.org is slowly running out of space. We should document the cleanup procedure so opening a tracker ticket. > Free disk space has dropped from 10% (61GB free) to 8.5% (52GB free) within the last week so we still have time to react. We can also modify alert thresholds or disable alerts if they're causing too much noise. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100091)

6 years, 1 month

1
0
0 / 0

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

6 years, 1 month

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra September 2018