June 2019 - Infra - oVirt List Archives

[CQ]: 100614, 3 (vdsm) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 13 Jun '19

13 Jun '19

A system test invoked by the "ovirt-4.3" change queue including change 100614,3 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 100623,1 (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 100623,1 (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/100614/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/100623/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1172/

1 0

[CQ]: 100614, 3 (vdsm) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 13 Jun '19

13 Jun '19

A system test invoked by the "ovirt-4.3" change queue including change 100614,3 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 100623,1 (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 100623,1 (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/100614/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/100623/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1170/

1 0

oVirt infra daily report - unstable production jobs - 854
by jenkins＠jenkins.phx.ovirt.org 13 Jun '19

13 Jun '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/854//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: a6f12ec (ovirt-ansible-vm-infra) failed "ovirt-master" system tests
by oVirt Jenkins 13 Jun '19

13 Jun '19

Change a6f12ec (ovirt-ansible-vm-infra) 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://github.com/oVirt/ovirt-ansible-vm-infra/commit/a6f12ec945adca1845c5… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14547/

1 0

[CQ]: 100614, 3 (vdsm) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Jun '19

12 Jun '19

A system test invoked by the "ovirt-4.3" change queue including change 100614,3 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 100623,1 (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 100623,1 (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/100614/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/100623/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1166/

1 0

[CQ]: 100343, 10 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Jun '19

12 Jun '19

A system test invoked by the "ovirt-master" change queue including change 100343,10 (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/100343/10 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/14545/

1 0

[CQ]: 100614, 3 (vdsm) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Jun '19

12 Jun '19

A system test invoked by the "ovirt-4.3" change queue including change 100614,3 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 100623,1 (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 100623,1 (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/100614/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/100623/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1161/

1 0

[CQ]: 100342, 9 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Jun '19

12 Jun '19

A system test invoked by the "ovirt-master" change queue including change 100342,9 (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/100342/9 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/14540/

1 0

[CQ]: 100699,1 (cockpit-ovirt) failed "ovirt-4.3" system tests
by oVirt Jenkins 12 Jun '19

12 Jun '19

Change 100699,1 (cockpit-ovirt) 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/100699/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1157/

1 0

[CQ]: 100479, 7 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Jun '19

12 Jun '19

A system test invoked by the "ovirt-master" change queue including change 100479,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/100479/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/14536/

1 0

[CQ]: 191ef46 (ovirt-ansible-hosted-engine-setup) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Jun '19

12 Jun '19

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/191ef4692… 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/e3cbb5de0… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1152/

1 0

[CQ]: 100341, 8 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Jun '19

12 Jun '19

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/

1 0

[CQ]: 100701,1 (ovirt-release) failed "ovirt-4.3" system tests
by oVirt Jenkins 12 Jun '19

12 Jun '19

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/

1 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 12 Jun '19

12 Jun '19

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/4758/… 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

1 0

[CQ]: 100480, 7 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Jun '19

12 Jun '19

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/

1 0

[oVirt Jenkins] ovirt-system-tests_compat-4.2-suite-master - Build # 606 - Failure!
by jenkins＠jenkins.phx.ovirt.org 12 Jun '19

12 Jun '19

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.

1 1

[CQ]: 100696,1 (ovirt-appliance) failed "ovirt-4.3" system tests
by oVirt Jenkins 12 Jun '19

12 Jun '19

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/

1 0

[CQ]: 100660, 6 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Jun '19

12 Jun '19

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/

1 0

oVirt infra daily report - unstable production jobs - 853
by jenkins＠jenkins.phx.ovirt.org 12 Jun '19

12 Jun '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/853//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 100695,1 (ovirt-node-ng-image) failed "ovirt-4.3" system tests
by oVirt Jenkins 11 Jun '19

11 Jun '19

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/

1 0

[CQ]: 100721, 2 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Jun '19

11 Jun '19

A system test invoked by the "ovirt-master" change queue including change 100721,2 (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/100721/2 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/14520/

1 0

[CQ]: 100241, 8 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Jun '19

11 Jun '19

A system test invoked by the "ovirt-master" change queue including change 100241,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/100241/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/14516/

1 0

[CQ]: e3cbb5d (ovirt-ansible-hosted-engine-setup) failed "ovirt-4.3" system tests
by oVirt Jenkins 11 Jun '19

11 Jun '19

Change e3cbb5d (ovirt-ansible-hosted-engine-setup) 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://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/e3cbb5de0… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1133/

1 0

[CQ]: 100437, 5 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Jun '19

11 Jun '19

A system test invoked by the "ovirt-master" change queue including change 100437,5 (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/100437/5 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/14512/

1 0

[CQ]: 99113, 3 (vdsm) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Jun '19

11 Jun '19

A system test invoked by the "ovirt-4.3" change queue including change 99113,3 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 100623,1 (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 100623,1 (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/99113/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/100623/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1128/

1 0

[CQ]: 100720, 1 (ovirt-engine-api-model) failed "ovirt-master" system tests
by oVirt Jenkins 11 Jun '19

11 Jun '19

Change 100720,1 (ovirt-engine-api-model) 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/100720/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14506/

1 0

[CQ]: 100665, 1 (ovirt-engine) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Jun '19

11 Jun '19

A system test invoked by the "ovirt-4.3" change queue including change 100665,1 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 100664,1 (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 100664,1 (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/100665/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/100664/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1123/

1 0

[JIRA] (OVIRT-2737) job failing on mock runner configuration missing
by Anton Marchukov (oVirt JIRA) 11 Jun '19

11 Jun '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2737?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-2737: -------------------------------------- Assignee: Ehud Yonasi (was: infra) > job failing on mock runner configuration missing > ------------------------------------------------ > > Key: OVIRT-2737 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2737 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: Ehud Yonasi > > looking at > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-imageio_standard… > and seems it's failing on missing mock runner configuration. > Discussing with Dafna she thinks basically mocker-epel-7-ppc64le.el7.cfg > shouldn't exist and the failure needs to be investigated. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100104)

1 0

[CQ]: 100664,1 (ovirt-engine) failed "ovirt-4.3" system tests
by oVirt Jenkins 11 Jun '19

11 Jun '19

Change 100664,1 (ovirt-engine) 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/100664/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1119/

1 0

[CQ]: e3cbb5d (ovirt-ansible-hosted-engine-setup) failed "ovirt-master" system tests
by oVirt Jenkins 11 Jun '19

11 Jun '19

Change e3cbb5d (ovirt-ansible-hosted-engine-setup) 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://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/e3cbb5de0… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14501/

2 1

[CQ]: 191ef46 (ovirt-ansible-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Jun '19

11 Jun '19

A system test invoked by the "ovirt-master" 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/191ef4692… 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/e3cbb5de0… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14503/

1 0

[CQ]: 99606, 8 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Jun '19

11 Jun '19

A system test invoked by the "ovirt-master" change queue including change 99606,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/99606/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/14502/

1 0

Build failed in Jenkins: system-sync_mirrors-centos-qemu-ev-release-el7-x86_64 #2136
by jenkins＠jenkins.phx.ovirt.org 11 Jun '19

11 Jun '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-qemu-ev-release-el7…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-qemu-ev-release-el7…> No credentials specified > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision ac4a2a5677786f11794c977c2c66fc76fab32aa0 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f ac4a2a5677786f11794c977c2c66fc76fab32aa0 Commit message: "change-queue-tester: Fix issue with hook caller" > git rev-list --no-walk ac4a2a5677786f11794c977c2c66fc76fab32aa0 # timeout=10 [system-sync_mirrors-centos-qemu-ev-release-el7-x86_64] $ /bin/bash -xe /tmp/jenkins4242977690705999186.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-qemu-ev-release-el7 x86_64 jenkins/data/mirrors-reposync.conf + MIRRORS_MP_BASE=/var/www/html/repos + MIRRORS_HTTP_BASE=http://mirrors.phx.ovirt.org/repos + MIRRORS_CACHE=/home/jenkins/mirrors_cache + MAX_LOCK_ATTEMPTS=120 + LOCK_WAIT_INTERVAL=5 + LOCK_BASE=/home/jenkins + OLD_MD_TO_KEEP=100 + HTTP_SELINUX_TYPE=httpd_sys_content_t + HTTP_FILE_MODE=644 + main resync_yum_mirror centos-qemu-ev-release-el7 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror centos-qemu-ev-release-el7 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=centos-qemu-ev-release-el7 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local sync_needed + mkdir -p /home/jenkins/mirrors_cache + verify_repo_fs centos-qemu-ev-release-el7 yum + local repo_name=centos-qemu-ev-release-el7 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/centos-qemu-ev-release-el7 /var/www/html/repos/yum/centos-qemu-ev-release-el7/base + check_yum_sync_needed centos-qemu-ev-release-el7 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=centos-qemu-ev-release-el7 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local p_sync_needed=sync_needed + local reposync_out + echo 'Checking if mirror needs a resync' Checking if mirror needs a resync + rm -rf /home/jenkins/mirrors_cache/centos-qemu-ev-release-el7 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync centos-qemu-ev-release-el7 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=centos-qemu-ev-release-el7 ++ local repo_arch=x86_64 ++ local reposync_conf=jenkins/data/mirrors-reposync.conf ++ extra_args=("${@:4}") ++ local extra_args ++ reposync --config=jenkins/data/mirrors-reposync.conf --repoid=centos-qemu-ev-release-el7 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/centos-qemu-ev-release-el7/base --norepopath --newest-only --urls --quiet Traceback (most recent call last): File "/usr/bin/reposync", line 373, in <module> main() File "/usr/bin/reposync", line 185, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1468, in _commonLoadRepoXML local = self.cachedir + '/repomd.xml' File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 777, in <lambda> cachedir = property(lambda self: self._dirGetAttr('cachedir')) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 760, in _dirGetAttr self.dirSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 738, in dirSetup self._dirSetupMkdir_p(dir) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 715, in _dirSetupMkdir_p raise Errors.RepoError, msg yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-qemu-ev-release-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-qemu-ev-release-el7' + reposync_out= Build step 'Execute shell' marked build as failure

1 1

oVirt infra daily report - unstable production jobs - 852
by jenkins＠jenkins.phx.ovirt.org 11 Jun '19

11 Jun '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/852//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 100469, 5 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 10 Jun '19

10 Jun '19

A system test invoked by the "ovirt-master" change queue including change 100469,5 (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/100469/5 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/14499/

1 0

[CQ]: 99113, 3 (vdsm) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 10 Jun '19

10 Jun '19

A system test invoked by the "ovirt-4.3" change queue including change 99113,3 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 100623,1 (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 100623,1 (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/99113/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/100623/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1116/

1 0

Jenkins build became unstable: ovirt_4.2_publish-rpms_nightly #637
by jenkins＠jenkins.phx.ovirt.org 10 Jun '19

10 Jun '19

See <http://jenkins.ovirt.org/job/ovirt_4.2_publish-rpms_nightly/637/display/red…>

1 3

[CQ]: 99113, 3 (vdsm) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 10 Jun '19

10 Jun '19

A system test invoked by the "ovirt-4.3" change queue including change 99113,3 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 100623,1 (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 100623,1 (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/99113/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/100623/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1112/

1 0

Change in ds-jenkins-stg[master]: add release branches
by review＠gerrit-staging.phx.ovirt.org 10 Jun '19

10 Jun '19

From Ehud Yonasi <eyonasi(a)redhat.com>: Ehud Yonasi has submitted this change and it was merged. ( https://gerrit-staging.phx.ovirt.org/253 ) Change subject: add release branches ...................................................................... add release branches Change-Id: I1d67d0f13fe787b0eceba14fc192d2ccd61cad17 Signed-off-by: Ehud Yonasi <eyonasi(a)redhat.com> --- A stdci.yaml 1 file changed, 2 insertions(+), 0 deletions(-) Approvals: Jenkins CI: Passed CI tests Ehud Yonasi: Looks good to me, approved; Verified -- To view, visit https://gerrit-staging.phx.ovirt.org/253 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: ds-jenkins-stg Gerrit-Branch: master Gerrit-MessageType: merged Gerrit-Change-Id: I1d67d0f13fe787b0eceba14fc192d2ccd61cad17 Gerrit-Change-Number: 253 Gerrit-PatchSet: 1 Gerrit-Owner: Ehud Yonasi <eyonasi(a)redhat.com> Gerrit-Reviewer: Ehud Yonasi <eyonasi(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

1 0

Change in ds-jenkins-stg[master]: add release branches
by review＠gerrit-staging.phx.ovirt.org 10 Jun '19

10 Jun '19

From Ehud Yonasi <eyonasi(a)redhat.com>: Ehud Yonasi has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/253 ) Change subject: add release branches ...................................................................... Patch Set 1: Verified+1 Code-Review+2 -- To view, visit https://gerrit-staging.phx.ovirt.org/253 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: ds-jenkins-stg Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: I1d67d0f13fe787b0eceba14fc192d2ccd61cad17 Gerrit-Change-Number: 253 Gerrit-PatchSet: 1 Gerrit-Owner: Ehud Yonasi <eyonasi(a)redhat.com> Gerrit-Reviewer: Ehud Yonasi <eyonasi(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Comment-Date: Mon, 10 Jun 2019 13:00:03 +0000 Gerrit-HasComments: No

1 0

planned gerrit downtime
by Evgheni Dereveanchin 10 Jun '19

10 Jun '19

Hi everyone, I will be migrating gerrit.ovirt.org to a different VM tonight so it will be unavailable for several hours as the process involves copying large amounts of data. It will not be possible to pull from or push to any repos as well as to review changes. I'll follow up as soon as the migration is complete. -- Regards, Evgheni Dereveanchin

3 4

Change in stdci-staging[master]: just a change
by review＠gerrit-staging.phx.ovirt.org 10 Jun '19

10 Jun '19

From Barak Korren <bkorren(a)redhat.com>: Barak Korren has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/215 ) Change subject: just a change ...................................................................... Patch Set 1: ci test please -- To view, visit https://gerrit-staging.phx.ovirt.org/215 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: stdci-staging Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: I6ad5ccb6da74775cd59597274439129b0e398609 Gerrit-Change-Number: 215 Gerrit-PatchSet: 1 Gerrit-Owner: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Comment-Date: Mon, 10 Jun 2019 07:31:59 +0000 Gerrit-HasComments: No

1 0

Change in stdci-staging[master]: just a change
by review＠gerrit-staging.phx.ovirt.org 10 Jun '19

10 Jun '19

From Barak Korren <bkorren(a)redhat.com>: Barak Korren has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/215 ) Change subject: just a change ...................................................................... Patch Set 1: ci please test -- To view, visit https://gerrit-staging.phx.ovirt.org/215 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: stdci-staging Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: I6ad5ccb6da74775cd59597274439129b0e398609 Gerrit-Change-Number: 215 Gerrit-PatchSet: 1 Gerrit-Owner: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Comment-Date: Mon, 10 Jun 2019 07:28:44 +0000 Gerrit-HasComments: No

1 0

Change in stdci-staging[master]: just a change
by review＠gerrit-staging.phx.ovirt.org 10 Jun '19

10 Jun '19

From Barak Korren <bkorren(a)redhat.com>: Barak Korren has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/215 ) Change subject: just a change ...................................................................... Patch Set 1: ci test please -- To view, visit https://gerrit-staging.phx.ovirt.org/215 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: stdci-staging Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: I6ad5ccb6da74775cd59597274439129b0e398609 Gerrit-Change-Number: 215 Gerrit-PatchSet: 1 Gerrit-Owner: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Comment-Date: Mon, 10 Jun 2019 07:23:26 +0000 Gerrit-HasComments: No

1 0

FC28 Blacklisted in oVirt STDCI V2
by Barak Korren 10 Jun '19

10 Jun '19

Hi all, By Snadro's request, as of a few minutes ago FC28 had been blacklisted in oVirt's STDCI V2 system. What this means is that if any project has FC28 threads configured in its STDCI V2 YAML configuration file, those threads will be ignored by the STDCI system and not invoked. Threads for building and testing on other distributions will keep working as before. It is still recommended that projects with fc28 configuration will patch their configuration files to remove FC28, to make it easier to understand what the CI does and not rely on an implicit blacklist. Please note that this only concerns projects that have made the switch to STDCI V2. Projects that still use V1, and have FC28 jobs defined, those jobs will keep working as before. The following patch by Sandro, however, includes code to remove all those jobs: https://gerrit.ovirt.org/c/100556/ Thanks, Barak. -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

1 0

oVirt infra daily report - unstable production jobs - 851
by jenkins＠jenkins.phx.ovirt.org 10 Jun '19

10 Jun '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/851//artifact/exported-a… Cheers, Jenkins

1 0

oVirt infra daily report - unstable production jobs - 850
by jenkins＠jenkins.phx.ovirt.org 09 Jun '19

09 Jun '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/850//artifact/exported-a… Cheers, Jenkins

1 0

Build failed in Jenkins: system-sync_mirrors-glusterfs-5-el7-x86_64 #418
by jenkins＠jenkins.phx.ovirt.org 08 Jun '19

08 Jun '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-glusterfs-5-el7-x86_64/418…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-glusterfs-5-el7-x86_64/ws/> No credentials specified > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision c41bdc92144d7ef87391521fca327d6e790624c1 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f c41bdc92144d7ef87391521fca327d6e790624c1 Commit message: "standard-stage: Remove pusher.py support in V1" > git rev-list --no-walk c41bdc92144d7ef87391521fca327d6e790624c1 # timeout=10 [system-sync_mirrors-glusterfs-5-el7-x86_64] $ /bin/bash -xe /tmp/jenkins7239729937118097042.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror glusterfs-5-el7 x86_64 jenkins/data/mirrors-reposync.conf + MIRRORS_MP_BASE=/var/www/html/repos + MIRRORS_HTTP_BASE=http://mirrors.phx.ovirt.org/repos + MIRRORS_CACHE=/home/jenkins/mirrors_cache + MAX_LOCK_ATTEMPTS=120 + LOCK_WAIT_INTERVAL=5 + LOCK_BASE=/home/jenkins + OLD_MD_TO_KEEP=100 + HTTP_SELINUX_TYPE=httpd_sys_content_t + HTTP_FILE_MODE=644 + main resync_yum_mirror glusterfs-5-el7 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror glusterfs-5-el7 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=glusterfs-5-el7 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local sync_needed + mkdir -p /home/jenkins/mirrors_cache + verify_repo_fs glusterfs-5-el7 yum + local repo_name=glusterfs-5-el7 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/glusterfs-5-el7 /var/www/html/repos/yum/glusterfs-5-el7/base + check_yum_sync_needed glusterfs-5-el7 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=glusterfs-5-el7 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local p_sync_needed=sync_needed + local reposync_out + echo 'Checking if mirror needs a resync' Checking if mirror needs a resync + rm -rf /home/jenkins/mirrors_cache/glusterfs-5-el7 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync glusterfs-5-el7 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=glusterfs-5-el7 ++ local repo_arch=x86_64 ++ local reposync_conf=jenkins/data/mirrors-reposync.conf ++ extra_args=("${@:4}") ++ local extra_args ++ reposync --config=jenkins/data/mirrors-reposync.conf --repoid=glusterfs-5-el7 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/glusterfs-5-el7/base --norepopath --newest-only --urls --quiet Traceback (most recent call last): File "/usr/bin/reposync", line 373, in <module> main() File "/usr/bin/reposync", line 185, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1468, in _commonLoadRepoXML local = self.cachedir + '/repomd.xml' File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 777, in <lambda> cachedir = property(lambda self: self._dirGetAttr('cachedir')) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 760, in _dirGetAttr self.dirSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 738, in dirSetup self._dirSetupMkdir_p(dir) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 715, in _dirSetupMkdir_p raise Errors.RepoError, msg yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/glusterfs-5-el7/packages error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/glusterfs-5-el7/packages' + reposync_out= Build step 'Execute shell' marked build as failure

1 1

[oVirt Jenkins] ovirt-system-tests_compat-4.2-suite-master - Build # 602 - Failure!
by jenkins＠jenkins.phx.ovirt.org 08 Jun '19

08 Jun '19

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/602/ Build Number: 602 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #602 [Eitan Raviv] networking: host fixture - import or create [Barak Korren] standard-stage: Remove pusher.py support in V1 ----------------- Failed Tests: ----------------- No tests ran.

1 1

oVirt infra daily report - unstable production jobs - 849
by jenkins＠jenkins.phx.ovirt.org 08 Jun '19

08 Jun '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/849//artifact/exported-a… Cheers, Jenkins

1 0