March 2019 - Infra - oVirt List Archives

oVirt infra daily report - unstable production jobs - 770
by jenkins＠jenkins.phx.ovirt.org 20 Mar '19

20 Mar '19

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/770//artifact/exported-a… Cheers, Jenkins

1 0

Change in stage-stdci1[master]: Add stdci.yaml for running in BM containers
by review＠gerrit-staging.phx.ovirt.org 20 Mar '19

20 Mar '19

From Barak Korren <bkorren(a)redhat.com>: Barak Korren has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/224 ) Change subject: Add stdci.yaml for running in BM containers ...................................................................... Patch Set 1: ci test -- To view, visit https://gerrit-staging.phx.ovirt.org/224 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: stage-stdci1 Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: I5d01cb9020468156774e3f2c220ee384ca2beb5d Gerrit-Change-Number: 224 Gerrit-PatchSet: 1 Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Comment-Date: Wed, 20 Mar 2019 14:31:54 +0000 Gerrit-HasComments: No

1 0

Change in stage-stdci1[master]: Add stdci.yaml for running in BM containers
by review＠gerrit-staging.phx.ovirt.org 20 Mar '19

20 Mar '19

From Barak Korren <bkorren(a)redhat.com>: Barak Korren has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/224 ) Change subject: Add stdci.yaml for running in BM containers ...................................................................... Patch Set 1: ci test -- To view, visit https://gerrit-staging.phx.ovirt.org/224 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: stage-stdci1 Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: I5d01cb9020468156774e3f2c220ee384ca2beb5d Gerrit-Change-Number: 224 Gerrit-PatchSet: 1 Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Comment-Date: Wed, 20 Mar 2019 14:07:00 +0000 Gerrit-HasComments: No

1 0

Change in stage-stdci1[master]: Add stdci.yaml for running in BM containers
by review＠gerrit-staging.phx.ovirt.org 20 Mar '19

20 Mar '19

From Barak Korren <bkorren(a)redhat.com>: Barak Korren has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/224 ) Change subject: Add stdci.yaml for running in BM containers ...................................................................... Patch Set 1: ci test please -- To view, visit https://gerrit-staging.phx.ovirt.org/224 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: stage-stdci1 Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: I5d01cb9020468156774e3f2c220ee384ca2beb5d Gerrit-Change-Number: 224 Gerrit-PatchSet: 1 Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Comment-Date: Wed, 20 Mar 2019 13:53:06 +0000 Gerrit-HasComments: No

1 0

[JENKINS] Failed to setup proejct ovirt-provider-ovn_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 20 Mar '19

20 Mar '19

Failed to run project_setup.sh for: #1888 ovirt-provider-ovn [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 vm0004.workers-phx.ovirt.org.

1 0

dwh failing on master, perhaps because engine is 4.4
by Yedidyah Bar David 20 Mar '19

20 Mar '19

Hi all, https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… fails with: ... lambda: engine.service('ovirt-engine-dwhd').alive() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 282, in assert_true_within_short assert_equals_within_short(func, True, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 266, in assert_equals_within_short func, value, SHORT_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 180 seconds dwhd log has: 2019-03-20 03:07:06|5iRyfJ|KapTFh|KapTFh|OVIRT_ENGINE_DWH|MinimalVersionCheck|Default|5|tDie|tDie_1|2019-03-20 03:07:06|You have upgraded your oVirt Engine and now require an upgrade of the ovirt-engine-dwh package. Please run engine-setup to upgrade the version. Service will now exit.|4 I assume that this is because the engine is now 4.4 and dwh master is still 4.3. I see that dwh already branched 4.3, should we bump master to 4.4? Thanks and best regards, -- Didi

1 0

[CQ]: 98527,5 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 19 Mar '19

19 Mar '19

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

1 0

oVirt infra daily report - unstable production jobs - 769
by jenkins＠jenkins.phx.ovirt.org 19 Mar '19

19 Mar '19

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/769//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 98614, 2 (ovirt-engine-metrics) failed "ovirt-master" system tests
by oVirt Jenkins 19 Mar '19

19 Mar '19

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

1 0

[CQ]: 98103,9 (ovirt-provider-ovn) failed "ovirt-4.3" system tests
by oVirt Jenkins 19 Mar '19

19 Mar '19

Change 98103,9 (ovirt-provider-ovn) 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/98103/9 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/281/

1 0