- Infra - oVirt List Archives

[JIRA] (OVIRT-1497) repoclosure fails on missing *libuv* pkg from centos-opstools-testing repo
by eedri (oVirt JIRA) 02 Jul '17

02 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1497?page=com.atlassian.jira.… ] eedri reassigned OVIRT-1497: ---------------------------- Assignee: Daniel Belenky (was: infra) Please check if its a cache issue, because it looks like its not failing the experimental flows. > repoclosure fails on missing *libuv* pkg from centos-opstools-testing repo > -------------------------------------------------------------------------- > > Key: OVIRT-1497 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1497 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: Daniel Belenky > Priority: Highest > > Hi, > just got into > package: 1:libuv-static-1.8.0-1.el7.x86_64 from internal_repo > unresolved deps: > libuv-devel = 1:1.8.0-1.el7 > within > http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_… > I'm now trying to figure out where this package comes from. > It's not in ovirt-master-snapshot-static. > I've found it on our internal mirror: > $ ssh mirrors.phx.ovirt.org > $ cd /var/www/html/repos/yum > $ find . -name "libuv*el7*" > ./centos-opstools-testing-el7/base/common/libuv-1.8.0-1.el7.x86_64.rpm > ./centos-opstools-testing-el7/base/common/libuv-devel-1.8.0-1.el7.x86_64.rpm > ./centos-opstools-testing-el7/base/common/libuv-static-1.8.0-1.el7.x86_64.rpm > ./centos-opstools-testing-el7/base/common/libuv-0.10.34-2.el7.x86_64.rpm > ./centos-opstools-testing-el7/base/common/libuv-devel-0.10.34-2.el7.x86_64.rpm > ./centos-opstools-testing-el7/base/common/libuv-static-0.10.34-2.el7.x86_64.rpm > ./epel-el7/base/l/libuv-1.10.2-1.el7.x86_64.rpm > ./epel-el7/base/l/libuv-devel-1.10.2-1.el7.x86_64.rpm > ./epel-el7/base/l/libuv-static-1.10.2-1.el7.x86_64.rpm > So looks like it comes from here. But the CentOS test repo has no such > package. > https://buildlogs.centos.org/centos/7/opstools/x86_64/common/ > has > libuv-0.10.34-2.el7.x86_64.rpm 2015-12-23 01:51 60K > libuv-devel-0.10.34-2.el7.x86_64.rpm 2015-12-23 01:51 40K > libuv-static-0.10.34-2.el7.x86_64.rpm 2015-12-23 01:51 59K > which is also a mistake since that package is not tagged to be there: > http://cbs.centos.org/koji/buildinfo?buildID=8182 > and isn't in > https://cbs.centos.org/repos/opstools7-common-testing/x86_64/os/ > (already reported to centos people) > Are we not syncing mirrors but just appending stuff? > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1497) repoclosure fails on missing *libuv* pkg from centos-opstools-testing repo
by eedri (oVirt JIRA) 02 Jul '17

02 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1497?page=com.atlassian.jira.… ] eedri updated OVIRT-1497: ------------------------- Priority: Highest (was: Medium) > repoclosure fails on missing *libuv* pkg from centos-opstools-testing repo > -------------------------------------------------------------------------- > > Key: OVIRT-1497 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1497 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > Priority: Highest > > Hi, > just got into > package: 1:libuv-static-1.8.0-1.el7.x86_64 from internal_repo > unresolved deps: > libuv-devel = 1:1.8.0-1.el7 > within > http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_… > I'm now trying to figure out where this package comes from. > It's not in ovirt-master-snapshot-static. > I've found it on our internal mirror: > $ ssh mirrors.phx.ovirt.org > $ cd /var/www/html/repos/yum > $ find . -name "libuv*el7*" > ./centos-opstools-testing-el7/base/common/libuv-1.8.0-1.el7.x86_64.rpm > ./centos-opstools-testing-el7/base/common/libuv-devel-1.8.0-1.el7.x86_64.rpm > ./centos-opstools-testing-el7/base/common/libuv-static-1.8.0-1.el7.x86_64.rpm > ./centos-opstools-testing-el7/base/common/libuv-0.10.34-2.el7.x86_64.rpm > ./centos-opstools-testing-el7/base/common/libuv-devel-0.10.34-2.el7.x86_64.rpm > ./centos-opstools-testing-el7/base/common/libuv-static-0.10.34-2.el7.x86_64.rpm > ./epel-el7/base/l/libuv-1.10.2-1.el7.x86_64.rpm > ./epel-el7/base/l/libuv-devel-1.10.2-1.el7.x86_64.rpm > ./epel-el7/base/l/libuv-static-1.10.2-1.el7.x86_64.rpm > So looks like it comes from here. But the CentOS test repo has no such > package. > https://buildlogs.centos.org/centos/7/opstools/x86_64/common/ > has > libuv-0.10.34-2.el7.x86_64.rpm 2015-12-23 01:51 60K > libuv-devel-0.10.34-2.el7.x86_64.rpm 2015-12-23 01:51 40K > libuv-static-0.10.34-2.el7.x86_64.rpm 2015-12-23 01:51 59K > which is also a mistake since that package is not tagged to be there: > http://cbs.centos.org/koji/buildinfo?buildID=8182 > and isn't in > https://cbs.centos.org/repos/opstools7-common-testing/x86_64/os/ > (already reported to centos people) > Are we not syncing mirrors but just appending stuff? > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1497) repoclosure fails on missing *libuv* pkg from centos-opstools-testing repo
by eedri (oVirt JIRA) 02 Jul '17

02 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1497?page=com.atlassian.jira.… ] eedri updated OVIRT-1497: ------------------------- Summary: repoclosure fails on missing *libuv* pkg from centos-opstools-testing repo (was: mirroring of upstream repos may be broken) > repoclosure fails on missing *libuv* pkg from centos-opstools-testing repo > -------------------------------------------------------------------------- > > Key: OVIRT-1497 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1497 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Hi, > just got into > package: 1:libuv-static-1.8.0-1.el7.x86_64 from internal_repo > unresolved deps: > libuv-devel = 1:1.8.0-1.el7 > within > http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_… > I'm now trying to figure out where this package comes from. > It's not in ovirt-master-snapshot-static. > I've found it on our internal mirror: > $ ssh mirrors.phx.ovirt.org > $ cd /var/www/html/repos/yum > $ find . -name "libuv*el7*" > ./centos-opstools-testing-el7/base/common/libuv-1.8.0-1.el7.x86_64.rpm > ./centos-opstools-testing-el7/base/common/libuv-devel-1.8.0-1.el7.x86_64.rpm > ./centos-opstools-testing-el7/base/common/libuv-static-1.8.0-1.el7.x86_64.rpm > ./centos-opstools-testing-el7/base/common/libuv-0.10.34-2.el7.x86_64.rpm > ./centos-opstools-testing-el7/base/common/libuv-devel-0.10.34-2.el7.x86_64.rpm > ./centos-opstools-testing-el7/base/common/libuv-static-0.10.34-2.el7.x86_64.rpm > ./epel-el7/base/l/libuv-1.10.2-1.el7.x86_64.rpm > ./epel-el7/base/l/libuv-devel-1.10.2-1.el7.x86_64.rpm > ./epel-el7/base/l/libuv-static-1.10.2-1.el7.x86_64.rpm > So looks like it comes from here. But the CentOS test repo has no such > package. > https://buildlogs.centos.org/centos/7/opstools/x86_64/common/ > has > libuv-0.10.34-2.el7.x86_64.rpm 2015-12-23 01:51 60K > libuv-devel-0.10.34-2.el7.x86_64.rpm 2015-12-23 01:51 40K > libuv-static-0.10.34-2.el7.x86_64.rpm 2015-12-23 01:51 59K > which is also a mistake since that package is not tagged to be there: > http://cbs.centos.org/koji/buildinfo?buildID=8182 > and isn't in > https://cbs.centos.org/repos/opstools7-common-testing/x86_64/os/ > (already reported to centos people) > Are we not syncing mirrors but just appending stuff? > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1497) mirroring of upstream repos may be broken
by eedri (oVirt JIRA) 02 Jul '17

02 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1497?page=com.atlassian.jira.… ] eedri commented on OVIRT-1497: ------------------------------ I'm pretty sure check-patch isn't using mirrors yet, so the problem isn't there. [1] It seems that we keep hitting issues originating from the centos ops tools testing repo, I suggest we'll remove it until we can find away to consume the release repo, or some other way to verify it before it hits OST. The amount of errors and issues we hit weekly due to repo closure is not realistic and doesn't justify the test itself IMO or the stability of OST and ease to test patches. [1] https://ovirt-jira.atlassian.net/browse/OST-33 > mirroring of upstream repos may be broken > ----------------------------------------- > > Key: OVIRT-1497 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1497 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Hi, > just got into > package: 1:libuv-static-1.8.0-1.el7.x86_64 from internal_repo > unresolved deps: > libuv-devel = 1:1.8.0-1.el7 > within > http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_… > I'm now trying to figure out where this package comes from. > It's not in ovirt-master-snapshot-static. > I've found it on our internal mirror: > $ ssh mirrors.phx.ovirt.org > $ cd /var/www/html/repos/yum > $ find . -name "libuv*el7*" > ./centos-opstools-testing-el7/base/common/libuv-1.8.0-1.el7.x86_64.rpm > ./centos-opstools-testing-el7/base/common/libuv-devel-1.8.0-1.el7.x86_64.rpm > ./centos-opstools-testing-el7/base/common/libuv-static-1.8.0-1.el7.x86_64.rpm > ./centos-opstools-testing-el7/base/common/libuv-0.10.34-2.el7.x86_64.rpm > ./centos-opstools-testing-el7/base/common/libuv-devel-0.10.34-2.el7.x86_64.rpm > ./centos-opstools-testing-el7/base/common/libuv-static-0.10.34-2.el7.x86_64.rpm > ./epel-el7/base/l/libuv-1.10.2-1.el7.x86_64.rpm > ./epel-el7/base/l/libuv-devel-1.10.2-1.el7.x86_64.rpm > ./epel-el7/base/l/libuv-static-1.10.2-1.el7.x86_64.rpm > So looks like it comes from here. But the CentOS test repo has no such > package. > https://buildlogs.centos.org/centos/7/opstools/x86_64/common/ > has > libuv-0.10.34-2.el7.x86_64.rpm 2015-12-23 01:51 60K > libuv-devel-0.10.34-2.el7.x86_64.rpm 2015-12-23 01:51 40K > libuv-static-0.10.34-2.el7.x86_64.rpm 2015-12-23 01:51 59K > which is also a mistake since that package is not tagged to be there: > http://cbs.centos.org/koji/buildinfo?buildID=8182 > and isn't in > https://cbs.centos.org/repos/opstools7-common-testing/x86_64/os/ > (already reported to centos people) > Are we not syncing mirrors but just appending stuff? > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[oVirt Jenkins] ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el7-x86_64 - Build # 267 - Failure!
by jenkins＠jenkins.phx.ovirt.org 02 Jul '17

02 Jul '17

------=_Part_69_1343012070.1498881934600 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el… Build Number: 267 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #267 ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_69_1343012070.1498881934600--

1 1

[oVirt Jenkins] ovirt-node-ng_ovirt-4.1_build-artifacts-el7-x86_64 - Build # 174 - Failure!
by jenkins＠jenkins.phx.ovirt.org 02 Jul '17

02 Jul '17

------=_Part_65_1191460841.1498881609477 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1_build-artifacts-el7-x8… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1_build-artifacts-el7-x8… Build Number: 174 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #174 ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_65_1191460841.1498881609477--

1 1

oVirt infra daily report - unstable production jobs - 370
by jenkins＠jenkins.phx.ovirt.org 01 Jul '17

01 Jul '17

------=_Part_77_596933735.1498950002460 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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/370//artifact/exported-a… Cheers, Jenkins ------=_Part_77_596933735.1498950002460 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 01/07/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.1_image-ng-system-tests/">ovirt_4.1_image-ng-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.1_publish-rpms_nightly/">ovirt_4.1_publish-rpms_nightly</a> </td><td> Collects RPMs from all oVirt projects (4.1 branches) and publish them to resources.ovirt.org yum repository.<br> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_he-system-tests/">ovirt_master_he-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_77_596933735.1498950002460--

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #7426 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 01 Jul '17

01 Jul '17

------=_Part_73_607813313.1498894383941 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/7426/, Build Number: 7426, Build Status: FAILURE ------=_Part_73_607813313.1498894383941--

1 1

[oVirt Jenkins] ovirt_4.1_hc-system-tests - Build # 121 - Failure!
by jenkins＠jenkins.phx.ovirt.org 01 Jul '17

01 Jul '17

------=_Part_37_1406022858.1498793848501 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt_4.1_hc-system-tests/ Build: http://jenkins.ovirt.org/job/ovirt_4.1_hc-system-tests/121/ Build Number: 121 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #121 [Shlomi Ben-David] Added host details to sso alternate engine fqdns ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.add_hosts Error Message: Host lago-hc-basic-suite-4-1-host1 failed to install -------------------- >> begin captured logging << -------------------- ovirtlago.testlib: ERROR: * Unhandled exception in <function _host_is_up at 0x4a30c08> Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 217, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt_4.1_hc-system-tests/ovirt-system-tests/hc-basic-suite-4.1/test-scenarios/002_bootstrap.py", line 150, in _host_is_up raise RuntimeError('Host %s failed to install' % host.name()) RuntimeError: Host lago-hc-basic-suite-4-1-host1 failed to install --------------------- >> 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 129, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/workspace/ovirt_4.1_hc-system-tests/ovirt-system-tests/hc-basic-suite-4.1/test-scenarios/002_bootstrap.py", line 163, in add_hosts testlib.assert_true_within(_host_is_up, timeout=15 * 60) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 256, in assert_true_within assert_equals_within(func, True, timeout, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 217, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt_4.1_hc-system-tests/ovirt-system-tests/hc-basic-suite-4.1/test-scenarios/002_bootstrap.py", line 150, in _host_is_up raise RuntimeError('Host %s failed to install' % host.name()) Host lago-hc-basic-suite-4-1-host1 failed to install -------------------- >> begin captured logging << -------------------- ovirtlago.testlib: ERROR: * Unhandled exception in <function _host_is_up at 0x4a30c08> Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 217, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt_4.1_hc-system-tests/ovirt-system-tests/hc-basic-suite-4.1/test-scenarios/002_bootstrap.py", line 150, in _host_is_up raise RuntimeError('Host %s failed to install' % host.name()) RuntimeError: Host lago-hc-basic-suite-4-1-host1 failed to install --------------------- >> end captured logging << --------------------- ------=_Part_37_1406022858.1498793848501--

1 1

oVirt infra daily report - unstable production jobs - 369
by jenkins＠jenkins.phx.ovirt.org 30 Jun '17

30 Jun '17

------=_Part_56_304817550.1498863602574 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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/369//artifact/exported-a… Cheers, Jenkins ------=_Part_56_304817550.1498863602574 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 30/06/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.1_hc-system-tests/">ovirt_4.1_hc-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_he-system-tests/">ovirt_master_he-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_56_304817550.1498863602574--

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #7421 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 30 Jun '17

30 Jun '17

------=_Part_50_1285335895.1498834264876 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/7421/, Build Number: 7421, Build Status: FAILURE ------=_Part_50_1285335895.1498834264876--

1 2

Change 78520,3 (ovirt-engine) failed system tests
by oVirt Jenkins 30 Jun '17

30 Jun '17

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

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #7417 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 30 Jun '17

30 Jun '17

------=_Part_39_1719722224.1498814774721 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/7417/, Build Number: 7417, Build Status: FAILURE ------=_Part_39_1719722224.1498814774721--

1 3

Change 77961,10 (ovirt-engine) failed system tests
by oVirt Jenkins 30 Jun '17

30 Jun '17

A system test invoked by the "ovirt-master" change queue including change 77961,10 (ovirt-engine) failed. However, this change seems not to be to root cause for failure. Change 78761,3 (ovirt-engine) that this change depends on or is based on, was detected to cause testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 78761,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/77961/10 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/78761/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1005/

1 0

ovirt-system-test failing on master
by Sandro Bonazzola 30 Jun '17

30 Jun '17

Hi, just an heads up ovirt-system-test is failing[1] on master for: [ ERROR ] Failed to execute stage 'Environment customization': [u'ovirt-engine-4.2.0-0.0.master.20170630084548.gitbbd011e.el7.centos.noarch requires openstack-java-keystone-model >= 3.1.2', u'ovirt-engine-4.2.0-0.0.master.20170630084548.gitbbd011e.el7.centos.noarch requires openstack-java-client >= 3.1.2', u'ovirt-engine-4.2.0-0.0.master.20170630084548.gitbbd011e.el7.centos.noarch requires openstack-java-glance-model >= 3.1.2', u'ovirt-engine-4.2.0-0.0.master.20170630084548.gitbbd011e.el7.centos.noarch requires openstack-java-glance-client >= 3.1.2', u'ovirt-engine-4.2.0-0.0.master.20170630084548.gitbbd011e.el7.centos.noarch requires openstack-java-resteasy-connector >= 3.1.2', u'ovirt-engine-4.2.0-0.0.master.20170630084548.gitbbd011e.el7.centos.noarch requires openstack-java-cinder-client >= 3.1.2', u'ovirt-engine-4.2.0-0.0.master.20170630084548.gitbbd011e.el7.centos.noarch requires openstack-java-quantum-model >= 3.1.2', u'ovirt-engine-4.2.0-0.0.master.20170630084548.gitbbd011e.el7.centos.noarch requires openstack-java-keystone-client >= 3.1.2', u'ovirt-engine-4.2.0-0.0.master.20170630084548.gitbbd011e.el7.centos.noarch requires openstack-java-quantum-client >= 3.1.2', u'ovirt-engine-4.2.0-0.0.master.20170630084548.gitbbd011e.el7.centos.noarch requires openstack-java-cinder-model >= 3.1.2'] after I merged https://gerrit.ovirt.org/#/c/78761/ Issue is that ovirt-system-test is using CentOS Virt SIG 4.0 repo instead of 4.2 repo as lookaside repo. Fixing patch is https://gerrit.ovirt.org/78248 ; I'm trying to get it merged since June 16th with no luck on Jenkins validation. If https://gerrit.ovirt.org/78248 won't be merged today please don't revert https://gerrit.ovirt.org/#/c/78761 but fix the root cause of eventual failures or we'll continue testing stuff having a test successful but wrong stuff tested. Thanks, [1] http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1000/testRepo… -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

2 1

[JIRA] (OVIRT-1497) mirroring of upstream repos may be broken
by sbonazzo (oVirt JIRA) 30 Jun '17

30 Jun '17

sbonazzo created OVIRT-1497: ------------------------------- Summary: mirroring of upstream repos may be broken Key: OVIRT-1497 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1497 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra Hi, just got into package: 1:libuv-static-1.8.0-1.el7.x86_64 from internal_repo unresolved deps: libuv-devel = 1:1.8.0-1.el7 within http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_… I'm now trying to figure out where this package comes from. It's not in ovirt-master-snapshot-static. I've found it on our internal mirror: $ ssh mirrors.phx.ovirt.org $ cd /var/www/html/repos/yum $ find . -name "libuv*el7*" ./centos-opstools-testing-el7/base/common/libuv-1.8.0-1.el7.x86_64.rpm ./centos-opstools-testing-el7/base/common/libuv-devel-1.8.0-1.el7.x86_64.rpm ./centos-opstools-testing-el7/base/common/libuv-static-1.8.0-1.el7.x86_64.rpm ./centos-opstools-testing-el7/base/common/libuv-0.10.34-2.el7.x86_64.rpm ./centos-opstools-testing-el7/base/common/libuv-devel-0.10.34-2.el7.x86_64.rpm ./centos-opstools-testing-el7/base/common/libuv-static-0.10.34-2.el7.x86_64.rpm ./epel-el7/base/l/libuv-1.10.2-1.el7.x86_64.rpm ./epel-el7/base/l/libuv-devel-1.10.2-1.el7.x86_64.rpm ./epel-el7/base/l/libuv-static-1.10.2-1.el7.x86_64.rpm So looks like it comes from here. But the CentOS test repo has no such package. https://buildlogs.centos.org/centos/7/opstools/x86_64/common/ has libuv-0.10.34-2.el7.x86_64.rpm 2015-12-23 01:51 60K libuv-devel-0.10.34-2.el7.x86_64.rpm 2015-12-23 01:51 40K libuv-static-0.10.34-2.el7.x86_64.rpm 2015-12-23 01:51 59K which is also a mistake since that package is not tagged to be there: http://cbs.centos.org/koji/buildinfo?buildID=8182 and isn't in https://cbs.centos.org/repos/opstools7-common-testing/x86_64/os/ (already reported to centos people) Are we not syncing mirrors but just appending stuff? -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

Change 78854,2 (ovirt-engine) failed system tests
by oVirt Jenkins 30 Jun '17

30 Jun '17

A system test invoked by the "ovirt-master" change queue including change 78854,2 (ovirt-engine) failed. However, this change seems not to be to root cause for failure. Change 78761,3 (ovirt-engine) that this change depends on or is based on, was detected to cause testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 78761,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/78854/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/78761/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1003/

1 0

Change 78853,1 (vdsm) failed system tests
by oVirt Jenkins 30 Jun '17

30 Jun '17

A system test invoked by the "ovirt-master" change queue including change 78853,1 (vdsm) failed. However, this change seems not to be to root cause for failure. Change 78806,5 (vdsm) that this change depends on or is based on, was detected to cause testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 78806,5 (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/78853/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/78806/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1001/

1 0

Change 78761,3 (ovirt-engine) failed system tests
by oVirt Jenkins 30 Jun '17

30 Jun '17

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

1 0

[JIRA] (OVIRT-1410) Please update #ovirt motd with oVirt 4.1.2
by Marc Dequènes (Duck) (oVirt JIRA) 30 Jun '17

30 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1410?page=com.atlassian.jira.… ] Marc Dequènes (Duck) updated OVIRT-1410: ---------------------------------------- Resolution: Fixed Status: Done (was: To Do) So in the end it was about the topic, not the ENTRYMSG. We asked apevec and he gave sbonazzo a bunch of new superpowers to be able to update the topic anytime :-). > Please update #ovirt motd with oVirt 4.1.2 > ------------------------------------------ > > Key: OVIRT-1410 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1410 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Joining #ovirt channel gives: > *oVirt 4.1.0 is now available. Please register your nick to participate in > this channel.* > Please, update with oVirt 4.1.2. > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

Change 78806,5 (vdsm) failed system tests
by oVirt Jenkins 30 Jun '17

30 Jun '17

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

1 0

[oVirt Jenkins] ovirt_4.1_system-tests_pre - Build # 176 - Failure!
by jenkins＠jenkins.phx.ovirt.org 29 Jun '17

29 Jun '17

------=_Part_82_1786067954.1498619171752 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt_4.1_system-tests_pre/ Build: http://jenkins.ovirt.org/job/ovirt_4.1_system-tests_pre/176/ Build Number: 176 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #176 [Daniel Belenky] Exclude packages from ovirt-master.repo [Barak Korren] Filter builds sent to change queues by version [Barak Korren] Make change queue invoke OST basic suit [Barak Korren] Various UX improvements in change-queue jobs [Barak Korren] Add a job for direct deployments to 'tested' [Barak Korren] Use new job to update 'tested' from experimental [Barak Korren] Use new tested deploy job in timed builders [Eyal Edri] update build retention policy for big artifacts ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 000_check_repo_closure.check_repo_closure Error Message: ## Params: ['repoclosure', '-t', '--config=/home/jenkins/workspace/ovirt_4.1_system-tests_pre/ovirt-system-tests/basic-suite-4.1/reposync-config.repo_repoclosure', '--lookaside=ovirt-4.1-el7', '--lookaside=ovirt-4.1-snapshot-static-el7', '--lookaside=ovirt-master-dependencies-el7', '--lookaside=glusterfs-3.8-el7', '--lookaside=centos-base-el7', '--lookaside=centos-updates-el7', '--lookaside=centos-extras-el7', '--lookaside=epel-el7', '--lookaside=centos-ovirt-4.0-el7', '--lookaside=centos-opstools-testing-el7', '--lookaside=copr-sac-gdeploy-el7', '--repoid=internal_repo']. ## Exist status: 1 ## Output: Reading in repository metadata - please wait.... Checking Dependencies Repos looked at: 12 centos-base-el7 centos-extras-el7 centos-opstools-testing-el7 centos-ovirt-4.0-el7 centos-updates-el7 copr-sac-gdeploy-el7 epel-el7 glusterfs-3.8-el7 internal_repo ovirt-4.1-el7 ovirt-4.1-snapshot-static-el7 ovirt-master-dependencies-el7 Num Packages in Repos: 25492 package: cockpit-ostree-138-1.el7.x86_64 from internal_repo unresolved deps: /usr/libexec/rpm-ostreed package: python2-botocore-1.4.43-1.el7.noarch from internal_repo unresolved deps: python-dateutil >= 0:2.1 Stack Trace: Traceback (most recent call last): 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 129, in wrapped_test test() File "/home/jenkins/workspace/ovirt_4.1_system-tests_pre/ovirt-system-tests/basic-suite-4.1/test-scenarios/000_check_repo_closure.py", line 105, in check_repo_closure raise RuntimeError(err_msg) RuntimeError: ## Params: ['repoclosure', '-t', '--config=/home/jenkins/workspace/ovirt_4.1_system-tests_pre/ovirt-system-tests/basic-suite-4.1/reposync-config.repo_repoclosure', '--lookaside=ovirt-4.1-el7', '--lookaside=ovirt-4.1-snapshot-static-el7', '--lookaside=ovirt-master-dependencies-el7', '--lookaside=glusterfs-3.8-el7', '--lookaside=centos-base-el7', '--lookaside=centos-updates-el7', '--lookaside=centos-extras-el7', '--lookaside=epel-el7', '--lookaside=centos-ovirt-4.0-el7', '--lookaside=centos-opstools-testing-el7', '--lookaside=copr-sac-gdeploy-el7', '--repoid=internal_repo']. ## Exist status: 1 ## Output: Reading in repository metadata - please wait.... Checking Dependencies Repos looked at: 12 centos-base-el7 centos-extras-el7 centos-opstools-testing-el7 centos-ovirt-4.0-el7 centos-updates-el7 copr-sac-gdeploy-el7 epel-el7 glusterfs-3.8-el7 internal_repo ovirt-4.1-el7 ovirt-4.1-snapshot-static-el7 ovirt-master-dependencies-el7 Num Packages in Repos: 25492 package: cockpit-ostree-138-1.el7.x86_64 from internal_repo unresolved deps: /usr/libexec/rpm-ostreed package: python2-botocore-1.4.43-1.el7.noarch from internal_repo unresolved deps: python-dateutil >= 0:2.1 ------=_Part_82_1786067954.1498619171752--

1 2

[oVirt Jenkins] ovirt_4.1_he-system-tests - Build # 165 - Failure!
by jenkins＠jenkins.phx.ovirt.org 29 Jun '17

29 Jun '17

------=_Part_137_1980968995.1498703520579 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt_4.1_he-system-tests/ Build: http://jenkins.ovirt.org/job/ovirt_4.1_he-system-tests/165/ Build Number: 165 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #165 [Shlomi Ben-David] Added host details to sso alternate engine fqdns ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_137_1980968995.1498703520579--

1 1

Change 78627,13 (vdsm) failed system tests
by oVirt Jenkins 29 Jun '17

29 Jun '17

Change 78627,13 (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/78627/13 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/994/

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #7412 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 29 Jun '17

29 Jun '17

------=_Part_22_939865630.1498769662167 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/7412/, Build Number: 7412, Build Status: FAILURE ------=_Part_22_939865630.1498769662167--

1 2

oVirt infra daily report - unstable production jobs - 368
by jenkins＠jenkins.phx.ovirt.org 29 Jun '17

29 Jun '17

------=_Part_26_2018086198.1498777202687 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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/368//artifact/exported-a… Cheers, Jenkins ------=_Part_26_2018086198.1498777202687 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 29/06/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.1_he-system-tests/">ovirt_4.1_he-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.1_system-tests_pre/">ovirt_4.1_system-tests_pre</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_he-system-tests/">ovirt_master_he-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/">test-repo_ovirt_experimental_master</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_26_2018086198.1498777202687--

1 0

Change 78810,1 (ovirt-host-deploy) failed system tests
by oVirt Jenkins 29 Jun '17

29 Jun '17

A system test invoked by the "ovirt-master" change queue including change 78810,1 (ovirt-host-deploy) failed. However, this change seems not to be to root cause for failure. Change 77650,1 (ovirt-host-deploy) that this change depends on or is based on, was detected to cause testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 77650,1 (ovirt-host-deploy) 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/78810/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/77650/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/984/

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #7408 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 29 Jun '17

29 Jun '17

------=_Part_18_1205556295.1498754431928 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/7408/, Build Number: 7408, Build Status: FAILURE ------=_Part_18_1205556295.1498754431928--

1 1

[oVirt Jenkins] standard-enqueue - Build #2163 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 29 Jun '17

29 Jun '17

------=_Part_13_443173573.1498747590304 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/standard-enqueue/2163/ Build Name: 2163 vdsm (3.6) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/78830 - title: virt: Use MIGRATABLE flag for _srcDomXML - project: vdsm - branch: ovirt-3.6 - author: Milan Zamazal <mzamazal(a)redhat.com> ------=_Part_13_443173573.1498747590304--

1 1

Change 78763,2 (ovirt-provider-ovn) failed system tests
by oVirt Jenkins 29 Jun '17

29 Jun '17

Change 78763,2 (ovirt-provider-ovn) 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/78763/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/981/

1 0

[JIRA] (OVIRT-1496) Mirrors can stay outdated for longer then 8 hours
by Barak Korren (oVirt JIRA) 29 Jun '17

29 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1496?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1496: ----------------------------------- Assignee: Barak Korren (was: infra) > Mirrors can stay outdated for longer then 8 hours > ------------------------------------------------- > > Key: OVIRT-1496 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1496 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: Barak Korren > Labels: mirrors > > We've seen cases where the mirrors can stay outdated despite having run the mirror sync jobs. This is probably due to yum metadata being cached. > We need to ensure the mirror sync jobs to not keep cached yum metadata for too long. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1496) Mirrors can stay outdated for longer then 8 hours
by Barak Korren (oVirt JIRA) 29 Jun '17

29 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1496?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1496: -------------------------------- Labels: mirrors (was: ) > Mirrors can stay outdated for longer then 8 hours > ------------------------------------------------- > > Key: OVIRT-1496 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1496 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > Labels: mirrors > > We've seen cases where the mirrors can stay outdated despite having run the mirror sync jobs. This is probably due to yum metadata being cached. > We need to ensure the mirror sync jobs to not keep cached yum metadata for too long. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1496) Mirrors can stay outdated for longer then 8 hours
by Barak Korren (oVirt JIRA) 29 Jun '17

29 Jun '17

Barak Korren created OVIRT-1496: ----------------------------------- Summary: Mirrors can stay outdated for longer then 8 hours Key: OVIRT-1496 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1496 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Repositories Mgmt Reporter: Barak Korren Assignee: infra We've seen cases where the mirrors can stay outdated despite having run the mirror sync jobs. This is probably due to yum metadata being cached. We need to ensure the mirror sync jobs to not keep cached yum metadata for too long. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1496) Mirrors can stay outdated for longer then 8 hours
by Barak Korren (oVirt JIRA) 29 Jun '17

29 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1496?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1496: -------------------------------- Epic Link: OVIRT-400 > Mirrors can stay outdated for longer then 8 hours > ------------------------------------------------- > > Key: OVIRT-1496 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1496 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > > We've seen cases where the mirrors can stay outdated despite having run the mirror sync jobs. This is probably due to yum metadata being cached. > We need to ensure the mirror sync jobs to not keep cached yum metadata for too long. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1468) Use CI mirrors for the slaves
by Barak Korren (oVirt JIRA) 29 Jun '17

29 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1468?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1468: ------------------------------------- Here are some thoughts about doing this from Jenkins. Besides reducing the need for external CM systems on the slaves this has another nice benefit where, because of the way the 'jenkins' repo is organised and tested, we can get CI for repo URL changes for "free". Essentially once we send a patch to the Jenkins repo that updates repo URLs for slaves, the updated configuration will be used in the '{{check-patch}}' run for that very patch. But this also raises an issue where if we send a broken patch, it will leave the slave that it ran on in a broken state. We can work around this by making the '{{check-patch.sh}}' script in the Jenkins repo rollback the configuration change on the slave. But there can be cases where we won't even get to '{{check-patch.sh}}', so we'll need to have some kind on a catch-all code that will revert changes to the slave in the case of breakage. Another way to look at this is to think in terms of a transaction. We will have a script that runs at the beginning of the job, "opens" a transaction and updates the slave repo configuration. The we will also have a script at the end of the job that "applies" the transaction if the job was successful or rolls it back otherwise. So we need a tool that can make the change transactional. This can probably be easily implemented by using some backup files (E.g. with '{{cp --backup}}'). But if we implement this ourselves in the 'jenkins' repo then we run the risk of having a patch that breaks the very rollback mechanism we're trying to provide... So we'll need transactional updated to the transactional updates tool... My brain starts to hurt from running in a loop now... Ok, let me try to get more practical: # We will need to either find a tool to allow setting repo configuration and rolling it back, or decide to implement this ourselves # However we choose to implement this we will probably need to call this from the '{{mock_setup.sh}}' script that get run at the start of every job. # We will need to add a new post-build step (publisher) that will only runs for successful jobs and applies the transaction # We will add code to '{{mock_cleanup.sh}}' to make it rollback the transaction if its has not been applied, and sort things so that it runs after the step mentioned in #3 above. # We will need to implement things so that the code that does rollback does not get updated in check-path. (But gets checked!) (As a side note, I know '{{mock_setup.sh}}' and '{{mock_cleanup.sh}}' need renaming, bare with me...) Since I mention some testing in #5, it may be a good idea to implement some of this in Python and use '{{pytest}}' (The 'jenkins' repo is already configured to run '{{pytest}}' tests), but we could also use '{{bats}}'. [~ederevea] would you like to take a swing at this yourself? > Use CI mirrors for the slaves > ----------------------------- > > Key: OVIRT-1468 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1468 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt Infra > Reporter: Barak Korren > Assignee: infra > Labels: jenkins, mirrors, slaves > > Since we've seen that issues like OVIRT-1467 can very quickly break our entire infrastructure, it may be advisable to use out mirrors to isolate the slave VMs from the upstream repos as well, and not just the testing environments. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #7401 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 29 Jun '17

29 Jun '17

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/7401/, Build Number: 7401, Build Status: FAILURE

1 1

[JIRA] (OVIRT-1495) Check out Gerrit metrics feature to see if we can push stats to graphana
by eedri (oVirt JIRA) 29 Jun '17

29 Jun '17

eedri created OVIRT-1495: ---------------------------- Summary: Check out Gerrit metrics feature to see if we can push stats to graphana Key: OVIRT-1495 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1495 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: eedri Assignee: infra Gerrit 2.13 added a new feature that allows sending metrics to an external source like Graphite. It would be interesting to see if we can push status about our Gerrit instance to our Graphana instance. More info at: https://gerrit-documentation.storage.googleapis.com/Documentation/2.13/metr… https://gerrit-documentation.storage.googleapis.com/Documentation/2.13/metr… -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1495) Check out Gerrit metrics feature to see if we can push stats to graphana
by eedri (oVirt JIRA) 29 Jun '17

29 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1495?page=com.atlassian.jira.… ] eedri updated OVIRT-1495: ------------------------- Epic Link: OVIRT-403 > Check out Gerrit metrics feature to see if we can push stats to graphana > ------------------------------------------------------------------------ > > Key: OVIRT-1495 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1495 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eedri > Assignee: infra > > Gerrit 2.13 added a new feature that allows sending metrics to an external source like Graphite. > It would be interesting to see if we can push status about our Gerrit instance to our Graphana instance. > More info at: > https://gerrit-documentation.storage.googleapis.com/Documentation/2.13/metr… > https://gerrit-documentation.storage.googleapis.com/Documentation/2.13/metr… -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

Change 78589,7 (vdsm) failed system tests
by oVirt Jenkins 29 Jun '17

29 Jun '17

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

1 0

[JIRA] (OVIRT-1493) Update current DR documentation with info on storage setup
by Evgheni Dereveanchin (oVirt JIRA) 29 Jun '17

29 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1493?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1493: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Update current DR documentation with info on storage setup > ---------------------------------------------------------- > > Key: OVIRT-1493 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1493 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eedri > Assignee: Evgheni Dereveanchin > Priority: Highest > > Following the last outage on oVirt storage servers, it seems that we are missing more info on how to debug and fix issues on the storage service. > current documentation on http://ovirt-infra-docs.readthedocs.io/en/latest/Phoenix_Lab/Storage_Hosts/… only shows configuration but doesn't include troubleshooting like what can we check or do in case any of the services that make the storage work fails. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1494) RCA for PHX Storage outage on 29.06.2017
by Evgheni Dereveanchin (oVirt JIRA) 29 Jun '17

29 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1494?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1494: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > RCA for PHX Storage outage on 29.06.2017 > ---------------------------------------- > > Key: OVIRT-1494 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1494 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > The PHX storage stopped working around 5:40 GMT today and was brought up manually at 9:12 GMT by shutting down ovirt-storage02 and starting services on the remaining node. > ovirt-storage02 was the active cluster member and some unknown condition triggered a cluster failover attempt. This event however failed with all cluster resources going offline and not coming up on either of the nodes until one of them was shut down completely. > Opening this ticket to analyze logs and confirm what triggered the failover and why it eventually failed. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1494) RCA for PHX Storage outage on 29.06.2017
by Evgheni Dereveanchin (oVirt JIRA) 29 Jun '17

29 Jun '17

Evgheni Dereveanchin created OVIRT-1494: ------------------------------------------- Summary: RCA for PHX Storage outage on 29.06.2017 Key: OVIRT-1494 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1494 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra The PHX storage stopped working around 5:40 GMT today and was brought up manually at 9:12 GMT by shutting down ovirt-storage02 and starting services on the remaining node. ovirt-storage02 was the active cluster member and some unknown condition triggered a cluster failover attempt. This event however failed with all cluster resources going offline and not coming up on either of the nodes until one of them was shut down completely. Opening this ticket to analyze logs and confirm what triggered the failover and why it eventually failed. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1490) Simplify oVirt storage configuration
by Evgheni Dereveanchin (oVirt JIRA) 29 Jun '17

29 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1490?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1490: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Simplify oVirt storage configuration > ------------------------------------ > > Key: OVIRT-1490 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1490 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: storage > Reporter: Barak Korren > Assignee: Evgheni Dereveanchin > Priority: Highest > Labels: infra, storage > > Today's outage was a clear reminder that our current storage configuration does not serve us well. We hardly know how to debug it, it seems to not be resistant to the very issues it was supposed to protect against and introduce potential failure scenarios of its own. > I suggest we implement a new storage layout that meets the following criteria: > # Ultimate simplicity at the lower level of the stack. More specifically: > ## The storage severs should be simple NFS or iSCSI servers. No DRBD and no exotic file-systems. > ## Only simple storage will be presented to oVirt for use as storage domains > # Separation of resources between critical services - The 'Jenkins" master for e.g. should not share resources with the "resources" server or anything else.The separation should hold true down to the physical spindle level. > # Duplication of services and use of local storage where possible - this is a longer term effort - but we have some low hanging fruits here like artifactory, where simple DNS/LB-based fail-over between two identical hosts would probably suffice. > # Complexity only where needed and up the stack. For example we can just have the storage for Jenkins be mirrored at the VM level with fail-over to a backup VM. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #7397 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 29 Jun '17

29 Jun '17

------=_Part_121_563702351.1498676196725 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/7397/, Build Number: 7397, Build Status: FAILURE ------=_Part_121_563702351.1498676196725--

1 2

[JIRA] (OVIRT-1490) Simplify oVirt storage configuration
by Barak Korren (oVirt JIRA) 29 Jun '17

29 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1490?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1490: -------------------------------- Summary: Simplify oVirt storage configuration (was: Simplify oVirt sotrage configuration) > Simplify oVirt storage configuration > ------------------------------------ > > Key: OVIRT-1490 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1490 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: storage > Reporter: Barak Korren > Assignee: infra > Priority: Highest > Labels: infra, storage > > Today's outage was a clear reminder that our current storage configuration does not serve us well. We hardly know how to debug it, it seems to not be resistant to the very issues it was supposed to protect against and introduce potential failure scenarios of its own. > I suggest we implement a new storage layout that meets the following criteria: > # Ultimate simplicity at the lower level of the stack. More specifically: > ## The storage severs should be simple NFS or iSCSI servers. No DRBD and no exotic file-systems. > ## Only simple storage will be presented to oVirt for use as storage domains > # Separation of resources between critical services - The 'Jenkins" master for e.g. should not share resources with the "resources" server or anything else.The separation should hold true down to the physical spindle level. > # Duplication of services and use of local storage where possible - this is a longer term effort - but we have some low hanging fruits here like artifactory, where simple DNS/LB-based fail-over between two identical hosts would probably suffice. > # Complexity only where needed and up the stack. For example we can just have the storage for Jenkins be mirrored at the VM level with fail-over to a backup VM. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #1783 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 29 Jun '17

29 Jun '17

------=_Part_60_1314560036.1498592982138 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/1783/, Build Number: 1783, Build Status: FAILURE ------=_Part_60_1314560036.1498592982138--

1 8

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #480
by jenkins＠jenkins.phx.ovirt.org 29 Jun '17

29 Jun '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/480/displa…> ------------------------------------------ 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-epel-el6-x86_64/ws/> > 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/changes/13/75913/5:patch --prune > git rev-parse origin/patch^{commit} # timeout=10 > git rev-parse patch^{commit} # timeout=10 Checking out Revision 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f (patch) > git config core.sparsecheckout # timeout=10 > git checkout -f 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f > git rev-list 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/hudson2203138297466724195.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, 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 96, in retrieveAllMD downloading = repo._commonRetrieveDataMD_list(mdtypes) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1609, in _commonRetrieveDataMD_list os.rename(local, local + '.old.tmp') OSError: [Errno 2] No such file or directory Build step 'Execute shell' marked build as failure

1 1

[JIRA] (OVIRT-1493) Update current DR documentation with info on storage setup
by eedri (oVirt JIRA) 29 Jun '17

29 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1493?page=com.atlassian.jira.… ] eedri updated OVIRT-1493: ------------------------- Epic Link: OVIRT-403 > Update current DR documentation with info on storage setup > ---------------------------------------------------------- > > Key: OVIRT-1493 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1493 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eedri > Assignee: infra > Priority: Highest > > Following the last outage on oVirt storage servers, it seems that we are missing more info on how to debug and fix issues on the storage service. > current documentation on http://ovirt-infra-docs.readthedocs.io/en/latest/Phoenix_Lab/Storage_Hosts/… only shows configuration but doesn't include troubleshooting like what can we check or do in case any of the services that make the storage work fails. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1493) Update current DR documentation with info on storage setup
by eedri (oVirt JIRA) 29 Jun '17

29 Jun '17

eedri created OVIRT-1493: ---------------------------- Summary: Update current DR documentation with info on storage setup Key: OVIRT-1493 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1493 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eedri Assignee: infra Priority: Highest Following the last outage on oVirt storage servers, it seems that we are missing more info on how to debug and fix issues on the storage service. current documentation on http://ovirt-infra-docs.readthedocs.io/en/latest/Phoenix_Lab/Storage_Hosts/… only shows configuration but doesn't include troubleshooting like what can we check or do in case any of the services that make the storage work fails. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

Build failed in Jenkins: system-sync_mirrors-centos-ovirt-4.0-el7-x86_64 #483
by jenkins＠jenkins.phx.ovirt.org 29 Jun '17

29 Jun '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-ovirt-4.0-el7-x86_6…> ------------------------------------------ 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-ovirt-4.0-el7-x86_6…> > 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/changes/13/75913/5:patch --prune > git rev-parse origin/patch^{commit} # timeout=10 > git rev-parse patch^{commit} # timeout=10 Checking out Revision 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f (patch) > git config core.sparsecheckout # timeout=10 > git checkout -f 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f > git rev-list 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f # timeout=10 [system-sync_mirrors-centos-ovirt-4.0-el7-x86_64] $ /bin/bash -xe /tmp/hudson2303515589631969475.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-ovirt-4.0-el7 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, 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 1465, in _commonLoadRepoXML if self._latestRepoXML(local): File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1443, in _latestRepoXML repomd = self.metalink_data.repomd File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 916, in <lambda> metalink_data = property(fget=lambda self: self._getMetalink(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 912, in _getMetalink self._metalink = metalink.MetaLinkRepoMD(self.metalink_filename) File "/usr/lib/python2.7/site-packages/yum/metalink.py", line 189, in __init__ raise MetaLinkRepoErrorParseFail, "File %s is not XML" % filename yum.metalink.MetaLinkRepoErrorParseFail: File /home/jenkins/mirrors_cache/fedora-updates-fc24/metalink.xml is not XML Build step 'Execute shell' marked build as failure

1 1