June 2019 - Infra - Ovirt List Archives

[CQ]: 191ef46 (ovirt-ansible-hosted-engine-setup) 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 191ef46 (ovirt-ansible-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change e3cbb5d (ovirt-ansible-hosted- engine-setup) 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 e3cbb5d (ovirt-ansible-hosted- engine-setup) 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/ovirt-ansible-hosted-engine-setup/commit/191ef46... For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/e3cbb5d... For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1152/

5 years, 4 months

1
0
0 / 0

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

5 years, 4 months

1
0
0 / 0

[CQ]: 100701,1 (ovirt-release) failed "ovirt-4.3" system tests

by oVirt Jenkins

Change 100701,1 (ovirt-release) is probably the reason behind recent system test failures in the "ovirt-4.3" 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/100701/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1148/

5 years, 4 months

1
0
0 / 0

Weird CI failure - lago ssh client output cut in the middle (was: Re: Change in ovirt-system-tests[master]: Rewrite local maintenance test)

by Yedidyah Bar David

On Tue, Jun 11, 2019 at 2:45 PM Code Review <gerrit(a)ovirt.org> wrote: > > From Jenkins CI <jenkins(a)ovirt.org>: > > Jenkins CI has posted comments on this change. > > Change subject: Rewrite local maintenance test > ...................................................................... > > > Patch Set 11: Continuous-Integration-1 > > Build Failed > > http://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/4758/ : FAILURE Only one suite failed, basic-suite-master. It failed with: https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/475... 2019-06-11 10:57:55,509::log_utils.py::__enter__::600::lago.ssh::DEBUG::start task:b2f51023-f985-4421-b096-930a187f09e7:Get ssh client for lago-he-basic-suite-master-host-0: 2019-06-11 10:57:59,391::log_utils.py::__exit__::611::lago.ssh::DEBUG::end task:b2f51023-f985-4421-b096-930a187f09e7:Get ssh client for lago-he-basic-suite-master-host-0: 2019-06-11 10:58:01,123::ssh.py::ssh::58::lago.ssh::DEBUG::Running c79824b8 on lago-he-basic-suite-master-host-0: hosted-engine --vm-status --json 2019-06-11 10:58:02,321::ssh.py::ssh::81::lago.ssh::DEBUG::Command c79824b8 on lago-he-basic-suite-master-host-0 returned with 0 2019-06-11 10:58:02,322::ssh.py::ssh::89::lago.ssh::DEBUG::Command c79824b8 on lago-he-basic-suite-master-host-0 output: {"1": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\nmetadata_feature_version=1\ntimestamp=5333 (Tue Jun 11 06:57:58 2019)\nhost-id=1\nscore=2671\nvm_conf_refresh_time=5334 (Tue Jun 11 06:57:59 2019)\nconf_on_shared_storage=True\nmaintenance=False\nstate=GlobalMaintenance\nstopped=False\n", "hostname": "lago-he-basic-suite-master-host-0.lago.local", "host-id": 1, "engine-status": {"reason": "failed liveliness check", "health": "bad", "vm": "up", "detail": "Up"}, "score": 2671, "stopped": false, "maintenance": false, "crc32": "0cc93af9", "local_conf_timestamp": 5334, "host-ts": 5333}, "2": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\nmetadata_feature_version=1\ntimestamp=5332 (Tue Jun 11 06:57:56 2019)\nhost-id=2\nscore=3400\nvm_conf_refresh_time=5332 (Tue Jun 11 06:57:56 2019)\nconf_on_shared_storage=True\nmaintenance=False\nstate=GlobalMaintenance\nstopped=False\n", "hostname": "lago-he-basic-suite-master-host-1", "host-id": 2019-06-11 10:58:02,322::testlib.py::assert_equals_within::242::ovirtlago.testlib::ERROR:: * Unhandled exception in <function <lambda> at 0x7f149ea0dd70> 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_standard-check-patch/ovirt-system-tests/he-basic-suite-master/test-scenarios/008_restart_he_vm.py", line 193, in <lambda> for k, v in _get_he_status(host).items() File "/home/jenkins/workspace/ovirt-system-tests_standard-check-patch/ovirt-system-tests/he-basic-suite-master/test-scenarios/008_restart_he_vm.py", line 134, in _get_he_status raise RuntimeError('could not parse JSON: %s' % ret.out) RuntimeError: could not parse JSON: {"1": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\nmetadata_feature_version=1\ntimestamp=5333 (Tue Jun 11 06:57:58 2019)\nhost-id=1\nscore=2671\nvm_conf_refresh_time=5334 (Tue Jun 11 06:57:59 2019)\nconf_on_shared_storage=True\nmaintenance=False\nstate=GlobalMaintenance\nstopped=False\n", "hostname": "lago-he-basic-suite-master-host-0.lago.local", "host-id": 1, "engine-status": {"reason": "failed liveliness check", "health": "bad", "vm": "up", "detail": "Up"}, "score": 2671, "stopped": false, "maintenance": false, "crc32": "0cc93af9", "local_conf_timestamp": 5334, "host-ts": 5333}, "2": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\nmetadata_feature_version=1\ntimestamp=5332 (Tue Jun 11 06:57:56 2019)\nhost-id=2\nscore=3400\nvm_conf_refresh_time=5332 (Tue Jun 11 06:57:56 2019)\nconf_on_shared_storage=True\nmaintenance=False\nstate=GlobalMaintenance\nstopped=False\n", "hostname": "lago-he-basic-suite-master-host-1", "host-id": Indeed, the json output from --vm-status is chopped in the middle, ending with: '"host-id": '. This can happen either due to the command writing only partial output (unlikely, imo), or some infra issue (lago, network, etc.). I am going to retrigger, anyway, but do not feel very good about this... Perhaps someone from infra can check this too - perhaps there was some infra issue on the host or something. Thanks, > > -- > To view, visit https://gerrit.ovirt.org/100570 > To unsubscribe, visit https://gerrit.ovirt.org/settings > > Gerrit-Project: ovirt-system-tests > Gerrit-Branch: master > Gerrit-MessageType: comment > Gerrit-Change-Id: I1c00426f65d92a5531415fee7c7b19ab0f4177e8 > Gerrit-Change-Number: 100570 > Gerrit-PatchSet: 11 > Gerrit-Owner: Yedidyah Bar David <didi(a)redhat.com> > Gerrit-Reviewer: Anton Marchukov <amarchuk(a)redhat.com> > Gerrit-Reviewer: Dafna Ron <dron(a)redhat.com> > Gerrit-Reviewer: Eyal Edri <eedri(a)redhat.com> > Gerrit-Reviewer: Gal Ben Haim <galbh2(a)gmail.com> > Gerrit-Reviewer: Galit Rosenthal <grosenth(a)redhat.com> > Gerrit-Reviewer: Jenkins CI <jenkins(a)ovirt.org> > Gerrit-Reviewer: Sandro Bonazzola <sbonazzo(a)redhat.com> > Gerrit-Reviewer: Simone Tiraboschi <stirabos(a)redhat.com> > Gerrit-Reviewer: Yedidyah Bar David <didi(a)redhat.com> > Gerrit-Comment-Date: Tue, 11 Jun 2019 11:45:03 +0000 > Gerrit-HasComments: No -- Didi

5 years, 4 months

1
0
0 / 0

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

5 years, 4 months

1
0
0 / 0

[oVirt Jenkins] ovirt-system-tests_compat-4.2-suite-master - Build # 606 - Failure!

by jenkins＠jenkins.phx.ovirt.org

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/606/ Build Number: 606 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #606 [Galit Rosenthal] Revert "Seperate test-scenrios dependency of 4.3 with master" [Barak Korren] stdci_runner: Allow blacklisting archs and distros [Barak Korren] Add hooks mechanisme to STDCI [Sandro Bonazzola] projects: drop fc28 jobs [Eyal Edri] drop mom v1 [Sandro Bonazzola] projects: add ovirt-log-collector to standard-pipelines [Barak Korren] change-queue-tester: Fix issue with hook caller ----------------- Failed Tests: ----------------- No tests ran.

5 years, 4 months

1
1
0 / 0

[CQ]: 100696,1 (ovirt-appliance) failed "ovirt-4.3" system tests

by oVirt Jenkins

Change 100696,1 (ovirt-appliance) is probably the reason behind recent system test failures in the "ovirt-4.3" 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/100696/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1143/

5 years, 4 months

1
0
0 / 0

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

5 years, 4 months

1
0
0 / 0

oVirt infra daily report - unstable production jobs - 853

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

5 years, 4 months

1
0
0 / 0

[CQ]: 100695,1 (ovirt-node-ng-image) failed "ovirt-4.3" system tests

by oVirt Jenkins

Change 100695,1 (ovirt-node-ng-image) is probably the reason behind recent system test failures in the "ovirt-4.3" 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/100695/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1138/

5 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra June 2019