- Infra - oVirt List Archives

[JIRA] (OVIRT-1452) Make change-queue email infra about failed changes
by Barak Korren (oVirt JIRA) 18 Jun '17

18 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1452?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1452: ----------------------------------- Assignee: Barak Korren (was: infra) > Make change-queue email infra about failed changes > -------------------------------------------------- > > Key: OVIRT-1452 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1452 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: Barak Korren > Labels: change-queue > > Before we add change status reporting to developers via Gerrit (OVIRT-1447) we should have it reported to the infra-list for a while to find issues. > We need to decide if this is a prerequisite for OVIRT-1446. -- This message was sent by Atlassian JIRA (v1000.1068.0#100050)

1 0

[JIRA] (OVIRT-1452) Make change-queue email infra about failed changes
by Barak Korren (oVirt JIRA) 18 Jun '17

18 Jun '17

Barak Korren created OVIRT-1452: ----------------------------------- Summary: Make change-queue email infra about failed changes Key: OVIRT-1452 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1452 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra Before we add change status reporting to developers via Gerrit (OVIRT-1447) we should have it reported to the infra-list for a while to find issues. We need to decide if this is a prerequisite for OVIRT-1446. -- This message was sent by Atlassian JIRA (v1000.1068.0#100050)

1 0

[JIRA] (OVIRT-1452) Make change-queue email infra about failed changes
by Barak Korren (oVirt JIRA) 18 Jun '17

18 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1452?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1452: -------------------------------- Epic Link: OVIRT-400 > Make change-queue email infra about failed changes > -------------------------------------------------- > > Key: OVIRT-1452 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1452 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > > Before we add change status reporting to developers via Gerrit (OVIRT-1447) we should have it reported to the infra-list for a while to find issues. > We need to decide if this is a prerequisite for OVIRT-1446. -- This message was sent by Atlassian JIRA (v1000.1068.0#100050)

1 0

[JIRA] (OVIRT-1451) Add a CI mirror for Gluster 3.10
by Barak Korren (oVirt JIRA) 18 Jun '17

18 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1451?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1451: ------------------------------------- [This patch|https://gerrit.ovirt.org/#/c/78246] makes OST HC suit use Gluster 3.10. This should probably be done before it is merged. Also see there for configuration details of the Gluster 3.10 repo. > Add a CI mirror for Gluster 3.10 > -------------------------------- > > Key: OVIRT-1451 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1451 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > Priority: High > > We currently have mirrors only for Gluster 3.6 and 3.8, since Gluster 3.10 was released, we need to add a mirror for it. > For more information about mirrors: > http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Transactional_mirrors/i… > The process to add mirrors is roughly: > # Create a patch to the 'jenkins' repo with: > ## Adding upstream repo configuration to the '{{data/mirrors-reposync.conf}}' file > ## Adding a mirror sync job to '{{jobs/confs/projects/system/sync_mirrors.yaml}}'. > # Verify patch by: > ## Running JJB to create the new sync job > ## Invoke the new sync job to see that it manages to sync the mirror for the 1st time > ## Wait a while to let the job get schedules and run on its own (sync jobs are scheduled every 8 hours by default) > As part of this work please document the process for adding a new mirror in infra-docs. -- This message was sent by Atlassian JIRA (v1000.1068.0#100050)

1 0

[JIRA] (OVIRT-1451) Add a CI mirror for Gluster 3.10
by Barak Korren (oVirt JIRA) 18 Jun '17

18 Jun '17

Barak Korren created OVIRT-1451: ----------------------------------- Summary: Add a CI mirror for Gluster 3.10 Key: OVIRT-1451 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1451 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Repositories Mgmt Reporter: Barak Korren Assignee: infra Priority: High We currently have mirrors only for Gluster 3.6 and 3.8, since Gluster 3.10 was released, we need to add a mirror for it. For more information about mirrors: http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Transactional_mirrors/i… The process to add mirrors is roughly: # Create a patch to the 'jenkins' repo with: ## Adding upstream repo configuration to the '{{data/mirrors-reposync.conf}}' file ## Adding a mirror sync job to '{{jobs/confs/projects/system/sync_mirrors.yaml}}'. # Verify patch by: ## Running JJB to create the new sync job ## Invoke the new sync job to see that it manages to sync the mirror for the 1st time ## Wait a while to let the job get schedules and run on its own (sync jobs are scheduled every 8 hours by default) As part of this work please document the process for adding a new mirror in infra-docs. -- This message was sent by Atlassian JIRA (v1000.1068.0#100050)

1 0

[JIRA] (OVIRT-1451) Add a CI mirror for Gluster 3.10
by Barak Korren (oVirt JIRA) 18 Jun '17

18 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1451?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1451: -------------------------------- Epic Link: OVIRT-403 > Add a CI mirror for Gluster 3.10 > -------------------------------- > > Key: OVIRT-1451 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1451 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > Priority: High > > We currently have mirrors only for Gluster 3.6 and 3.8, since Gluster 3.10 was released, we need to add a mirror for it. > For more information about mirrors: > http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Transactional_mirrors/i… > The process to add mirrors is roughly: > # Create a patch to the 'jenkins' repo with: > ## Adding upstream repo configuration to the '{{data/mirrors-reposync.conf}}' file > ## Adding a mirror sync job to '{{jobs/confs/projects/system/sync_mirrors.yaml}}'. > # Verify patch by: > ## Running JJB to create the new sync job > ## Invoke the new sync job to see that it manages to sync the mirror for the 1st time > ## Wait a while to let the job get schedules and run on its own (sync jobs are scheduled every 8 hours by default) > As part of this work please document the process for adding a new mirror in infra-docs. -- This message was sent by Atlassian JIRA (v1000.1068.0#100050)

1 0

[oVirt Jenkins] ovirt-node-ng_master_build-artifacts-el7-x86_64 - Build # 442 - Failure!
by jenkins＠jenkins.phx.ovirt.org 18 Jun '17

18 Jun '17

------=_Part_499_2112676597.1497672285605 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… Build Number: 442 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #442 ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_499_2112676597.1497672285605--

1 1

[oVirt Jenkins] ovirt-node-ng_ovirt-4.1-snapshot_build-artifacts-el7-x86_64 - Build # 161 - Failure!
by jenkins＠jenkins.phx.ovirt.org 18 Jun '17

18 Jun '17

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

1 2

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

18 Jun '17

------=_Part_501_483171734.1497672319779 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: 250 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #250 ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_501_483171734.1497672319779--

1 1

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

17 Jun '17

------=_Part_509_49548724.1497740403514 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/356//artifact/exported-a… Cheers, Jenkins ------=_Part_509_49548724.1497740403514 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 - 17/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_master-ansible-system-tests/">ovirt_master-ansible-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_hc-system-tests/">ovirt_master_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_image-ng-system-tests/">ovirt_master_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/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_509_49548724.1497740403514--

1 0

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

17 Jun '17

------=_Part_497_151130303.1497672008546 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: 158 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #158 ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_497_151130303.1497672008546--

1 1

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #507
by jenkins＠jenkins.phx.ovirt.org 16 Jun '17

16 Jun '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> ------------------------------------------ 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-updates-el7-x86_64/…> > 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-updates-el7-x86_64] $ /bin/bash -xe /tmp/hudson5631380543897415904.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-updates-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 904, in _getMetalink shutil.move(result, self.metalink_filename) File "/usr/lib64/python2.7/shutil.py", line 301, in move copy2(src, real_dst) File "/usr/lib64/python2.7/shutil.py", line 130, in copy2 copyfile(src, dst) File "/usr/lib64/python2.7/shutil.py", line 82, in copyfile with open(src, 'rb') as fsrc: IOError: [Errno 2] No such file or directory: '/home/jenkins/mirrors_cache/fedora-updates-fc26/metalink.xml.tmp' Build step 'Execute shell' marked build as failure

1 1

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

16 Jun '17

------=_Part_479_419339635.1497654001734 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/355//artifact/exported-a… Cheers, Jenkins ------=_Part_479_419339635.1497654001734 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 - 16/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/system-sync_mirrors-centos-updates-el7-x86_64/">system-sync_mirrors-centos-updates-el7-x86_64</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_479_419339635.1497654001734--

1 0

[JIRA] (OVIRT-1450) Update gerrit to 2.14
by eedri (oVirt JIRA) 16 Jun '17

16 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1450?page=com.atlassian.jira.… ] eedri commented on OVIRT-1450: ------------------------------ This is probably a duplicate, we already plan to upgrade Gerrit to 2.13 soon, 2.14 will follow if all goes well. Evgheni is on PTO today, so he can reply with dates on the planned upgrade to 2.13 early next week. We also want to make sure the Gerrit backups are verified and working well before upgrading. On Fri, Jun 16, 2017 at 8:08 AM, sbonazzo (oVirt JIRA) < -- Eyal edri ASSOCIATE MANAGER RHV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) > Update gerrit to 2.14 > --------------------- > > Key: OVIRT-1450 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1450 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > We are using 2.12.7 on gerrit.ovirt.org while 2.14.1 is available: > https://www.gerritcodereview.com/releases/2.14.md > An interesting feature is the possibility to set an assignee for a review. > And it has a bunch of bugfixes. > -- > 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.1068.0#100050)

1 0

[JIRA] (OVIRT-1450) Update gerrit to 2.14
by sbonazzo (oVirt JIRA) 16 Jun '17

16 Jun '17

sbonazzo created OVIRT-1450: ------------------------------- Summary: Update gerrit to 2.14 Key: OVIRT-1450 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1450 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra We are using 2.12.7 on gerrit.ovirt.org while 2.14.1 is available: https://www.gerritcodereview.com/releases/2.14.md An interesting feature is the possibility to set an assignee for a review. And it has a bunch of bugfixes. -- 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.1068.0#100050)

2 1

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

15 Jun '17

------=_Part_448_1958926703.1497567601423 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/354//artifact/exported-a… Cheers, Jenkins ------=_Part_448_1958926703.1497567601423 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 - 15/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_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/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_448_1958926703.1497567601423--

1 0

[JIRA] (OVIRT-1449) Add upgrade suits to change-queue tests
by Barak Korren (oVirt JIRA) 15 Jun '17

15 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1449?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1449: ----------------------------------- Assignee: Barak Korren (was: infra) > Add upgrade suits to change-queue tests > --------------------------------------- > > Key: OVIRT-1449 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1449 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: Barak Korren > Labels: change-queue > > The change queue tester jobs currently only run the basic suits. > We need to add the upgrade suits as, but need to ensure we have enough hardware first, or alternatively disable 'experimental'. -- This message was sent by Atlassian JIRA (v1000.1065.1#100048)

1 0

[JIRA] (OVIRT-1449) Add upgrade suits to change-queue tests
by Barak Korren (oVirt JIRA) 15 Jun '17

15 Jun '17

Barak Korren created OVIRT-1449: ----------------------------------- Summary: Add upgrade suits to change-queue tests Key: OVIRT-1449 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1449 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra The change queue tester jobs currently only run the basic suits. We need to add the upgrade suits as, but need to ensure we have enough hardware first, or alternatively disable 'experimental'. -- This message was sent by Atlassian JIRA (v1000.1065.1#100048)

1 0

[JIRA] (OVIRT-1449) Add upgrade suits to change-queue tests
by Barak Korren (oVirt JIRA) 15 Jun '17

15 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1449?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1449: -------------------------------- Epic Link: OVIRT-400 > Add upgrade suits to change-queue tests > --------------------------------------- > > Key: OVIRT-1449 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1449 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > > The change queue tester jobs currently only run the basic suits. > We need to add the upgrade suits as, but need to ensure we have enough hardware first, or alternatively disable 'experimental'. -- This message was sent by Atlassian JIRA (v1000.1065.1#100048)

1 0

[JIRA] (OVIRT-1448) Enable devs to specifiy patch dependencies for OST
by Barak Korren (oVirt JIRA) 15 Jun '17

15 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1448?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1448: -------------------------------- Description: We have an issue with our system ATM where if there are patches for different projects that depend on one another, the system is unaware of that dependency. What typically happens in this scenario is that sending the dependent patch makes the experimental test fail and keep failing until the other patch is also merged. The change queue will handle this better, but the typical behaviour for it would be to reject both patches, unless they are somehow coordinated to make it into the same test. The change queue core code already includes the ability to track and understand dependencies between changes. What is missing is the ability for developers to specify theses dependencies. We would probably want to adopt OpenStack's convention here. > Enable devs to specifiy patch dependencies for OST > -------------------------------------------------- > > Key: OVIRT-1448 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1448 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > > We have an issue with our system ATM where if there are patches for different projects that depend on one another, the system is unaware of that dependency. > What typically happens in this scenario is that sending the dependent patch makes the experimental test fail and keep failing until the other patch is also merged. > The change queue will handle this better, but the typical behaviour for it would be to reject both patches, unless they are somehow coordinated to make it into the same test. > The change queue core code already includes the ability to track and understand dependencies between changes. What is missing is the ability for developers to specify theses dependencies. > We would probably want to adopt OpenStack's convention here. -- This message was sent by Atlassian JIRA (v1000.1065.1#100048)

1 0

[JIRA] (OVIRT-1448) Enable devs to specifiy patch dependencies for OST
by Barak Korren (oVirt JIRA) 15 Jun '17

15 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1448?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1448: -------------------------------- Labels: change-queue (was: ) > Enable devs to specifiy patch dependencies for OST > -------------------------------------------------- > > Key: OVIRT-1448 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1448 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > -- This message was sent by Atlassian JIRA (v1000.1065.1#100048)

1 0

[JIRA] (OVIRT-1448) Enable devs to specifiy patch dependencies for OST
by Barak Korren (oVirt JIRA) 15 Jun '17

15 Jun '17

Barak Korren created OVIRT-1448: ----------------------------------- Summary: Enable devs to specifiy patch dependencies for OST Key: OVIRT-1448 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1448 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra -- This message was sent by Atlassian JIRA (v1000.1065.1#100048)

1 0

[JIRA] (OVIRT-1448) Enable devs to specifiy patch dependencies for OST
by Barak Korren (oVirt JIRA) 15 Jun '17

15 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1448?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1448: -------------------------------- Epic Link: OVIRT-400 > Enable devs to specifiy patch dependencies for OST > -------------------------------------------------- > > Key: OVIRT-1448 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1448 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.1065.1#100048)

1 0

[JIRA] (OVIRT-1447) Make change-queue report status to Gerrit
by Barak Korren (oVirt JIRA) 15 Jun '17

15 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1447?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1447: ----------------------------------- Assignee: Barak Korren (was: infra) > Make change-queue report status to Gerrit > ----------------------------------------- > > Key: OVIRT-1447 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1447 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: Barak Korren > > While the basic capabilities for the change-queue to report to Gerrit were already implemented, this had not been enabled yet in order to avoid spamming developers with incorrect messages while the change-queue is still being tested. > Once we are confident that the change queue is working well, we can add reporting to Gerrit. -- This message was sent by Atlassian JIRA (v1000.1065.1#100048)

1 0

[JIRA] (OVIRT-1447) Make change-queue report status to Gerrit
by Barak Korren (oVirt JIRA) 15 Jun '17

15 Jun '17

Barak Korren created OVIRT-1447: ----------------------------------- Summary: Make change-queue report status to Gerrit Key: OVIRT-1447 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1447 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra While the basic capabilities for the change-queue to report to Gerrit were already implemented, this had not been enabled yet in order to avoid spamming developers with incorrect messages while the change-queue is still being tested. Once we are confident that the change queue is working well, we can add reporting to Gerrit. -- This message was sent by Atlassian JIRA (v1000.1065.1#100048)

1 0

[JIRA] (OVIRT-1447) Make change-queue report status to Gerrit
by Barak Korren (oVirt JIRA) 15 Jun '17

15 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1447?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1447: -------------------------------- Epic Link: OVIRT-400 > Make change-queue report status to Gerrit > ----------------------------------------- > > Key: OVIRT-1447 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1447 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > > While the basic capabilities for the change-queue to report to Gerrit were already implemented, this had not been enabled yet in order to avoid spamming developers with incorrect messages while the change-queue is still being tested. > Once we are confident that the change queue is working well, we can add reporting to Gerrit. -- This message was sent by Atlassian JIRA (v1000.1065.1#100048)

1 0

[JIRA] (OVIRT-1446) Make the change-queue jobs update the 'tested' repo
by Barak Korren (oVirt JIRA) 15 Jun '17

15 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1446?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1446: -------------------------------- Description: The 'tested' repo is currently being updated by the 'experimental' jobs, this means that as soon as something makes experimental fail, changes stop flowing into 'tested'. When the change-queue will update 'tested' only the failing changes will be blocked. Until this is done, the change queue is not really testing stuff properly, because while experimental is failing, changes that pass the CQ successfully are just dropped instead of being kept. was: The 'tested' repo is current;y being updated by the 'experimental' jobs, this means that as soon as something makes experimental fail, changes stop flowing into 'tested'. When the change-queue will update 'tested' only the failing changes will be blocked. Until this is done, the change queue is not really testing stuff properly, because while experimental is failing, changes that pass the CQ successfully are just dropped instead of being kept. > Make the change-queue jobs update the 'tested' repo > --------------------------------------------------- > > Key: OVIRT-1446 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1446 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > > The 'tested' repo is currently being updated by the 'experimental' jobs, this means that as soon as something makes experimental fail, changes stop flowing into 'tested'. > When the change-queue will update 'tested' only the failing changes will be blocked. > Until this is done, the change queue is not really testing stuff properly, because while experimental is failing, changes that pass the CQ successfully are just dropped instead of being kept. -- This message was sent by Atlassian JIRA (v1000.1065.1#100048)

1 0

[JIRA] (OVIRT-1446) Make the change-queue jobs update the 'tested' repo
by Barak Korren (oVirt JIRA) 15 Jun '17

15 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1446?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1446: -------------------------------- Epic Link: OVIRT-400 > Make the change-queue jobs update the 'tested' repo > --------------------------------------------------- > > Key: OVIRT-1446 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1446 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > > The 'tested' repo is current;y being updated by the 'experimental' jobs, this means that as soon as something makes experimental fail, changes stop flowing into 'tested'. > When the change-queue will update 'tested' only the failing changes will be blocked. > Until this is done, the change queue is not really testing stuff properly, because while experimental is failing, changes that pass the CQ successfully are just dropped instead of being kept. -- This message was sent by Atlassian JIRA (v1000.1065.1#100048)

1 0

[JIRA] (OVIRT-1446) Make the change-queue jobs update the 'tested' repo
by Barak Korren (oVirt JIRA) 15 Jun '17

15 Jun '17

Barak Korren created OVIRT-1446: ----------------------------------- Summary: Make the change-queue jobs update the 'tested' repo Key: OVIRT-1446 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1446 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra The 'tested' repo is current;y being updated by the 'experimental' jobs, this means that as soon as something makes experimental fail, changes stop flowing into 'tested'. When the change-queue will update 'tested' only the failing changes will be blocked. Until this is done, the change queue is not really testing stuff properly, because while experimental is failing, changes that pass the CQ successfully are just dropped instead of being kept. -- This message was sent by Atlassian JIRA (v1000.1065.1#100048)

1 0

[JIRA] (OVIRT-1445) Gate OST sources change in change-queue test jobs
by Barak Korren (oVirt JIRA) 15 Jun '17

15 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1445?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1445: ----------------------------------- Assignee: Barak Korren (was: infra) > Gate OST sources change in change-queue test jobs > -------------------------------------------------- > > Key: OVIRT-1445 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1445 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: Barak Korren > > Since the OST source code can affect tests results we should gate changes to it in tests jobs and not just blindly use 'master'. > The idea is to send merged patches to OST as changes to the change queue, and have the change queue tester jobs track the last commit for which the tests passed successfully. -- This message was sent by Atlassian JIRA (v1000.1065.1#100048)

1 0

[JIRA] (OVIRT-1445) Gate OST sources change in change-queue test jobs
by Barak Korren (oVirt JIRA) 15 Jun '17

15 Jun '17

Barak Korren created OVIRT-1445: ----------------------------------- Summary: Gate OST sources change in change-queue test jobs Key: OVIRT-1445 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1445 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra Since the OST source code can affect tests results we should gate changes to it in tests jobs and not just blindly use 'master'. The idea is to send merged patches to OST as changes to the change queue, and have the change queue tester jobs track the last commit for which the tests passed successfully. -- This message was sent by Atlassian JIRA (v1000.1065.1#100048)

1 0

[JIRA] (OVIRT-1445) Gate OST sources change in change-queue test jobs
by Barak Korren (oVirt JIRA) 15 Jun '17

15 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1445?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1445: -------------------------------- Epic Link: OVIRT-400 > Gate OST sources change in change-queue test jobs > -------------------------------------------------- > > Key: OVIRT-1445 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1445 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > > Since the OST source code can affect tests results we should gate changes to it in tests jobs and not just blindly use 'master'. > The idea is to send merged patches to OST as changes to the change queue, and have the change queue tester jobs track the last commit for which the tests passed successfully. -- This message was sent by Atlassian JIRA (v1000.1065.1#100048)

1 0

[JIRA] (OVIRT-1444) Gate mirror changes in change-queue jobs
by Barak Korren (oVirt JIRA) 15 Jun '17

15 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1444?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1444: ----------------------------------- Assignee: Barak Korren (was: infra) > Gate mirror changes in change-queue jobs > ---------------------------------------- > > Key: OVIRT-1444 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1444 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: Barak Korren > Labels: change-queue > > When mirrors change, make the new snapshot be submitted as a change to the change queues. > The change queue test jobs will in turn be switched to not use the latest mirror snapshots and instead track which mirror snapshot successfully passed tests. > This will effectively provide gating for upstream repo changes. -- This message was sent by Atlassian JIRA (v1000.1065.1#100048)

1 0

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

15 Jun '17

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

1 1

[JIRA] (OVIRT-1444) Gate mirror changes in change-queue jobs
by Barak Korren (oVirt JIRA) 15 Jun '17

15 Jun '17

Barak Korren created OVIRT-1444: ----------------------------------- Summary: Gate mirror changes in change-queue jobs Key: OVIRT-1444 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1444 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra When mirrors change, make the new snapshot be submitted as a change to the change queues. The change queue test jobs will in turn be switched to not use the latest mirror snapshots and instead track which mirror snapshot successfully passed tests. This will effectively provide gating for upstream repo changes. -- This message was sent by Atlassian JIRA (v1000.1065.1#100048)

1 0

[JIRA] (OVIRT-1444) Gate mirror changes in change-queue jobs
by Barak Korren (oVirt JIRA) 15 Jun '17

15 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1444?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1444: -------------------------------- Epic Link: OVIRT-400 > Gate mirror changes in change-queue jobs > ---------------------------------------- > > Key: OVIRT-1444 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1444 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > > When mirrors change, make the new snapshot be submitted as a change to the change queues. > The change queue test jobs will in turn be switched to not use the latest mirror snapshots and instead track which mirror snapshot successfully passed tests. > This will effectively provide gating for upstream repo changes. -- This message was sent by Atlassian JIRA (v1000.1065.1#100048)

1 0

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

15 Jun '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/435/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/hudson1786334846940847910.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Not using downloaded repomd.xml because it is older than what we have: Current : Wed Jun 14 02:40:28 2017 Downloaded: Sun Jun 11 17:37:33 2017 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 1494, in _commonLoadRepoXML self._revertOldRepoXML() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1323, in _revertOldRepoXML os.rename(old_data['old_local'], old_data['local']) OSError: [Errno 2] No such file or directory Build step 'Execute shell' marked build as failure

1 1

python-sdk4 builds for FC26 on PPC64LE are constantly failing
by Barak Korren 15 Jun '17

15 Jun '17

See here: http://jenkins.ovirt.org/job/python-ovirt-engine-sdk4_master_build-artifact… Do we even want this build? Is FC26 on PPC64 usable? Looks like there are a bunch of missing packages. -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

2 1

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #501
by jenkins＠jenkins.phx.ovirt.org 14 Jun '17

14 Jun '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> ------------------------------------------ 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-updates-el7-x86_64/…> > 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-updates-el7-x86_64] $ /bin/bash -xe /tmp/hudson8025271032904376196.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-updates-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 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

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

14 Jun '17

------=_Part_379_359593749.1497481201710 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/353//artifact/exported-a… Cheers, Jenkins ------=_Part_379_359593749.1497481201710 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 - 14/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/system-sync_mirrors-centos-updates-el7-x86_64/">system-sync_mirrors-centos-updates-el7-x86_64</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_379_359593749.1497481201710--

1 0

Re: [ovirt-devel] [ovirt-system-tests] Failed after fluentd rpm ubdate
by Eyal Edri 14 Jun '17

14 Jun '17

Adding infra as well. Currently, master OST is still failing on this. http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/7189/testR… On Wed, Jun 14, 2017 at 4:54 PM, Sandro Bonazzola <sbonazzo(a)redhat.com> wrote: > > > On Wed, Jun 14, 2017 at 3:50 PM, Yedidyah Bar David <didi(a)redhat.com> > wrote: > >> On Wed, Jun 14, 2017 at 4:44 PM, Gil Shinar <gshinar(a)redhat.com> wrote: >> > This patch fixes the chgrp but not we see: >> > >> > Unable to start service fluentd: Job for fluentd.service failed because >> > start of the service was attempted too often >> >> Adding Shirly. >> >> Do we collect syslog (/var/log/messages or journalctl)? If so, we can try >> to see why it fails. >> > > Adding also Richard who may be interested on this. > > >> >> > >> > >> > On Wed, Jun 14, 2017 at 12:29 PM, Yedidyah Bar David <didi(a)redhat.com> >> > wrote: >> >> >> >> On Wed, Jun 14, 2017 at 11:34 AM, Valentina Makarova >> >> <makarovavs07(a)gmail.com> wrote: >> >> > Hello! >> >> > >> >> > Fluentd packages was modified yesterday there >> >> > >> >> > http://resources.ovirt.org/pub/ovirt-master-snapshot-static/ >> rpm/el7/noarch/ >> >> > This repository is referenced in reposync-config. >> >> > >> >> > And now run_suile.sh failed in 003_00_metrics_bootstrap test with >> error: >> >> > TASK [fluentd : Ensure fluentd configuration directory exists] >> >> > ***************** fatal: [localhost]: FAILED! => {"changed": false, >> >> > "failed": true, "gid": 0, "group": "root", "mode": "0755", "msg": >> "chgrp >> >> > failed: failed to look up group fluentd" >> >> > >> >> > And the same error on host0 and hos1. >> >> > >> >> > Does anyone know how to fix it? >> >> >> >> Should be fixed by [1]. Either wait for the repos to be updated or >> install >> >> the update from jenkins (link to it inside [1]). >> >> >> >> [1] https://gerrit.ovirt.org/#/c/78140/ >> >> >> >> > >> >> > Sincerely, Valentina Makarova >> >> > >> >> > >> >> > _______________________________________________ >> >> > Devel mailing list >> >> > Devel(a)ovirt.org >> >> > http://lists.ovirt.org/mailman/listinfo/devel >> >> >> >> >> >> >> >> -- >> >> Didi >> >> _______________________________________________ >> >> Devel mailing list >> >> Devel(a)ovirt.org >> >> http://lists.ovirt.org/mailman/listinfo/devel >> > >> > >> >> >> >> -- >> Didi >> _______________________________________________ >> Devel mailing list >> Devel(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/devel >> > > > > -- > > 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> > > _______________________________________________ > Devel mailing list > Devel(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel > -- Eyal edri ASSOCIATE MANAGER RHV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

2 1

[oVirt Jenkins] ovirt-appliance_ovirt-4.1-snapshot_build-artifacts-el7-x86_64 - Build # 184 - Failure!
by jenkins＠jenkins.phx.ovirt.org 14 Jun '17

14 Jun '17

------=_Part_324_1874063996.1497366515870 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.1-snapshot_build-artif… Build: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.1-snapshot_build-artif… Build Number: 184 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #184 [Gil Shinar] Configured ovirt-host to use on-change instead of timed [Sandro Bonazzola] ovirt-host: drop fc26 and ppc64le [Yuval Turgeman] Revert "engine-appliance: build in selinux enforcing mode" ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_324_1874063996.1497366515870--

1 1

[JIRA] (OVIRT-1441) [RFE] Add a jenkins job for copying external packages to static repos
by Barak Korren (oVirt JIRA) 14 Jun '17

14 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1441?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1441: ------------------------------------- So again, I see 3 types of packages: 1. 3rd party packages for which an RPM is available for an official and reliable source (e.g. CentOS, Fedora) 2. 3rd party packages where there is no RPM avialable and we want to ship an RPM with oVirt 3. oVirt packages For the 1st case we setup the 3rd party repo in the '*release*.rpm'. For the 3rd case the package is usually built and managed by the CI systems. We seem to be dealing with the 2nd case here, the solution for that was to make an oVirt "adapter" source repo with a usual build-artifacts job that creates or downloads the RPM. One is runs, the rest works just like for packages of the 3rd case. Since we want to track and gate changes to oVirt, the "adapter" repo should be made so that is downloads a very specific version of the 3rd party package. That way getting an updated version of the upstream package requires a patch to the adapter repo which can be tracked and gated. See also discussion in OVIRT-1299. > [RFE] Add a jenkins job for copying external packages to static repos > --------------------------------------------------------------------- > > Key: OVIRT-1441 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1441 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > Description of problem: > Currently, when we want to copy a package from elsewhere to > resources.ovirt.org, we manually run repoman. It will be nice to have > a jenkins job for this - with inputs probably being URLs of source > packages/repos and target versions to copy to: > 1. It will not require us anymore to login there and do sensitive > stuff on it directly > 2. It will have proper logs, allowing much more easily understand when > a package was added, by whom, and even perhaps why. So better add to > the inputs also 'Notes'. > This is cloned from: > https://bugzilla.redhat.com/show_bug.cgi?id=1455316 > Best, > -- > Didi -- This message was sent by Atlassian JIRA (v1000.1045.3#100046)

1 0

[JIRA] (OVIRT-1441) [RFE] Add a jenkins job for copying external packages to static repos
by Yedidyah Bar David (oVirt JIRA) 14 Jun '17

14 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1441?page=com.atlassian.jira.… ] Yedidyah Bar David commented on OVIRT-1441: ------------------------------------------- On Wed, Jun 14, 2017 at 3:33 PM, Barak Korren (oVirt JIRA) That's a good question from oVirt-metrics' perspective. I am not sure. For now we wanted something quick and this was the solution - build in copr, copy to -static. I am not saying it's the best solution. I did open the other ticket... I am just suggesting it as a real-life use-case that we should consider when designing how to compose our repos etc. -- Didi > [RFE] Add a jenkins job for copying external packages to static repos > --------------------------------------------------------------------- > > Key: OVIRT-1441 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1441 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > Description of problem: > Currently, when we want to copy a package from elsewhere to > resources.ovirt.org, we manually run repoman. It will be nice to have > a jenkins job for this - with inputs probably being URLs of source > packages/repos and target versions to copy to: > 1. It will not require us anymore to login there and do sensitive > stuff on it directly > 2. It will have proper logs, allowing much more easily understand when > a package was added, by whom, and even perhaps why. So better add to > the inputs also 'Notes'. > This is cloned from: > https://bugzilla.redhat.com/show_bug.cgi?id=1455316 > Best, > -- > Didi -- This message was sent by Atlassian JIRA (v1000.1045.3#100046)

1 0

[JIRA] (OVIRT-1441) [RFE] Add a jenkins job for copying external packages to static repos
by Barak Korren (oVirt JIRA) 14 Jun '17

14 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1441?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1441: ------------------------------------- So how are we going to deal with this feature when targeting Fedora? Maybe we can ask them to just build for Fedora too? > [RFE] Add a jenkins job for copying external packages to static repos > --------------------------------------------------------------------- > > Key: OVIRT-1441 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1441 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > Description of problem: > Currently, when we want to copy a package from elsewhere to > resources.ovirt.org, we manually run repoman. It will be nice to have > a jenkins job for this - with inputs probably being URLs of source > packages/repos and target versions to copy to: > 1. It will not require us anymore to login there and do sensitive > stuff on it directly > 2. It will have proper logs, allowing much more easily understand when > a package was added, by whom, and even perhaps why. So better add to > the inputs also 'Notes'. > This is cloned from: > https://bugzilla.redhat.com/show_bug.cgi?id=1455316 > Best, > -- > Didi -- This message was sent by Atlassian JIRA (v1000.1045.3#100046)

1 0

[JIRA] (OVIRT-1441) [RFE] Add a jenkins job for copying external packages to static repos
by Yedidyah Bar David (oVirt JIRA) 14 Jun '17

14 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1441?page=com.atlassian.jira.… ] Yedidyah Bar David commented on OVIRT-1441: ------------------------------------------- On Wed, Jun 14, 2017 at 3:12 PM, Barak Korren (oVirt JIRA) IIRC they do build it in centos-opstools, but not for fedora. -- Didi > [RFE] Add a jenkins job for copying external packages to static repos > --------------------------------------------------------------------- > > Key: OVIRT-1441 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1441 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > Description of problem: > Currently, when we want to copy a package from elsewhere to > resources.ovirt.org, we manually run repoman. It will be nice to have > a jenkins job for this - with inputs probably being URLs of source > packages/repos and target versions to copy to: > 1. It will not require us anymore to login there and do sensitive > stuff on it directly > 2. It will have proper logs, allowing much more easily understand when > a package was added, by whom, and even perhaps why. So better add to > the inputs also 'Notes'. > This is cloned from: > https://bugzilla.redhat.com/show_bug.cgi?id=1455316 > Best, > -- > Didi -- This message was sent by Atlassian JIRA (v1000.1045.3#100046)

1 0

[JIRA] (OVIRT-1441) [RFE] Add a jenkins job for copying external packages to static repos
by Barak Korren (oVirt JIRA) 14 Jun '17

14 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1441?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1441: ------------------------------------- I'm guessing the copr functionality is based on some existing tools in Fedora and/or CentOS, so perhaps its just a matter of finding out what those are... As long as the package is going to be an oVirt dependency, and it is not shipped by anyone else, its better to move it through the oVirt CI process. If the upstream will release official RPMs at some point we can switch to mirroring their repos for the CI system. > [RFE] Add a jenkins job for copying external packages to static repos > --------------------------------------------------------------------- > > Key: OVIRT-1441 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1441 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > Description of problem: > Currently, when we want to copy a package from elsewhere to > resources.ovirt.org, we manually run repoman. It will be nice to have > a jenkins job for this - with inputs probably being URLs of source > packages/repos and target versions to copy to: > 1. It will not require us anymore to login there and do sensitive > stuff on it directly > 2. It will have proper logs, allowing much more easily understand when > a package was added, by whom, and even perhaps why. So better add to > the inputs also 'Notes'. > This is cloned from: > https://bugzilla.redhat.com/show_bug.cgi?id=1455316 > Best, > -- > Didi -- This message was sent by Atlassian JIRA (v1000.1045.3#100046)

1 0

[JIRA] (OVIRT-1441) [RFE] Add a jenkins job for copying external packages to static repos
by Yedidyah Bar David (oVirt JIRA) 14 Jun '17

14 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1441?page=com.atlassian.jira.… ] Yedidyah Bar David commented on OVIRT-1441: ------------------------------------------- On Wed, Jun 14, 2017 at 2:24 PM, Barak Korren (oVirt JIRA) That's indeed an option. This specific project is not really part of oVirt, IIUC. It will be used as part of the common-logging effort, aka https://github.com/ViaQ . Actually this was the first time I built a rubygem in copr (and one of the first few times I built anything. But I did have an account), and it was as simple as choosing a build type rubygem and passing the link to it. I don't think we can beat that yet... -- Didi > [RFE] Add a jenkins job for copying external packages to static repos > --------------------------------------------------------------------- > > Key: OVIRT-1441 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1441 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > Description of problem: > Currently, when we want to copy a package from elsewhere to > resources.ovirt.org, we manually run repoman. It will be nice to have > a jenkins job for this - with inputs probably being URLs of source > packages/repos and target versions to copy to: > 1. It will not require us anymore to login there and do sensitive > stuff on it directly > 2. It will have proper logs, allowing much more easily understand when > a package was added, by whom, and even perhaps why. So better add to > the inputs also 'Notes'. > This is cloned from: > https://bugzilla.redhat.com/show_bug.cgi?id=1455316 > Best, > -- > Didi -- This message was sent by Atlassian JIRA (v1000.1045.3#100046)

1 0

[JIRA] (OVIRT-1441) [RFE] Add a jenkins job for copying external packages to static repos
by Barak Korren (oVirt JIRA) 14 Jun '17

14 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1441?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1441: ------------------------------------- See the path that the UX team took, they have "adapter" projects that get the dependencies from the upstream sources and then build the ovirt-specific packages from them. You can have your project run the build in copr, but it should be just as simple to just run the build on our hardware and not depend on an external service. > [RFE] Add a jenkins job for copying external packages to static repos > --------------------------------------------------------------------- > > Key: OVIRT-1441 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1441 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > Description of problem: > Currently, when we want to copy a package from elsewhere to > resources.ovirt.org, we manually run repoman. It will be nice to have > a jenkins job for this - with inputs probably being URLs of source > packages/repos and target versions to copy to: > 1. It will not require us anymore to login there and do sensitive > stuff on it directly > 2. It will have proper logs, allowing much more easily understand when > a package was added, by whom, and even perhaps why. So better add to > the inputs also 'Notes'. > This is cloned from: > https://bugzilla.redhat.com/show_bug.cgi?id=1455316 > Best, > -- > Didi -- This message was sent by Atlassian JIRA (v1000.1045.3#100046)

1 0

[JIRA] (OVIRT-1443) Create on-demand manual job for the metrics project
by Gil Shinar (oVirt JIRA) 14 Jun '17

14 Jun '17

Gil Shinar created OVIRT-1443: --------------------------------- Summary: Create on-demand manual job for the metrics project Key: OVIRT-1443 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1443 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Gil Shinar Assignee: infra -- This message was sent by Atlassian JIRA (v1000.1045.3#100046)

1 0