- Infra - oVirt List Archives

[JIRA] (OVIRT-1161) Nightly publisher is broken
by Barak Korren (oVirt JIRA) 19 Feb '17

19 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1161?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1161: ----------------------------------- Assignee: Barak Korren (was: infra) > Nightly publisher is broken > --------------------------- > > Key: OVIRT-1161 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1161 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: Barak Korren > Priority: Highest > > Nightly publisher is currently broken, this has caused some of the oVirt snapshot repos to become empty, which in turn caused OST failures, among others. > The error output from the nightly publisher job is as follows: > {code} > [/usr/local/libexec/releng-tools/scan_for_artifacts.sh] ##### Starting artifacts publishing Sun Feb 19 09:00:01 UTC 2017 > FATAL: We still have files under /home/jenkins/artifacts/ovirt-master-snapshot.ready. Please recheck > FATAL: Failed inside the loop > {code} > This is probably caused by YUM metadata that has been placed in the {{/home/jenkins/artifacts/ovirt-master-snapshot.ready}} by repoman that had been added in OVIRT-1152. > This as also surfaced another issue - if the {{\*-snapshot.ready}} directory exists while the nightly publisher job runs (which means the cron job did not finish yet), it will happily move the {{\*-snaphot.tmp}} directory into it. What it should do instead is wait a while for it to vanish, and then fail if it does not. -- This message was sent by Atlassian JIRA (v1000.769.1#100032)

1 0

[JIRA] (OVIRT-1161) Nightly publisher is broken
by Barak Korren (oVirt JIRA) 19 Feb '17

19 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1161?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1161: -------------------------------- Description: Nightly publisher is currently broken, this has caused some of the oVirt snapshot repos to become empty, which in turn caused OST failures, among others. The error output from the nightly publisher job is as follows: {code} [/usr/local/libexec/releng-tools/scan_for_artifacts.sh] ##### Starting artifacts publishing Sun Feb 19 09:00:01 UTC 2017 FATAL: We still have files under /home/jenkins/artifacts/ovirt-master-snapshot.ready. Please recheck FATAL: Failed inside the loop {code} This is probably caused by YUM metadata that has been placed in the {{/home/jenkins/artifacts/ovirt-master-snapshot.ready}} by repoman that had been added in OVIRT-1152. This as also surfaced another issue - if the {{\*-snapshot.ready}} directory exists while the nightly publisher job runs (which means the cron job did not finish yet), it will happily move the {{\*-snaphot.tmp}} directory into it. What it should do instead is wait a while for it to vanish, and then fail if it does not. was: Nightly publisher is currently broken, this has caused some of the oVirt snapshot repos to become empty, which in turn caused OST failures, among others. The error output from the nightly publisher job is as follows: {code} [/usr/local/libexec/releng-tools/scan_for_artifacts.sh] ##### Starting artifacts publishing Sun Feb 19 09:00:01 UTC 2017 FATAL: We still have files under /home/jenkins/artifacts/ovirt-master-snapshot.ready. Please recheck FATAL: Failed inside the loop {code} This is probably caused by YUM metadata that has been placed in the {{/home/jenkins/artifacts/ovirt-master-snapshot.ready}} by repoman that had been added in OVIRT-1152. This as also surfaced another issue - if the {{*-snapshot.ready}} directory exists while the nightly publisher job runs (which means the cron job did not finish yet), it will happily move the {{*-snaphot.tmp}} directory into it. What it should do instead is wait a while for it to vanish, and then fail if it does not. > Nightly publisher is broken > --------------------------- > > Key: OVIRT-1161 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1161 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > Priority: Highest > > Nightly publisher is currently broken, this has caused some of the oVirt snapshot repos to become empty, which in turn caused OST failures, among others. > The error output from the nightly publisher job is as follows: > {code} > [/usr/local/libexec/releng-tools/scan_for_artifacts.sh] ##### Starting artifacts publishing Sun Feb 19 09:00:01 UTC 2017 > FATAL: We still have files under /home/jenkins/artifacts/ovirt-master-snapshot.ready. Please recheck > FATAL: Failed inside the loop > {code} > This is probably caused by YUM metadata that has been placed in the {{/home/jenkins/artifacts/ovirt-master-snapshot.ready}} by repoman that had been added in OVIRT-1152. > This as also surfaced another issue - if the {{\*-snapshot.ready}} directory exists while the nightly publisher job runs (which means the cron job did not finish yet), it will happily move the {{\*-snaphot.tmp}} directory into it. What it should do instead is wait a while for it to vanish, and then fail if it does not. -- This message was sent by Atlassian JIRA (v1000.769.1#100032)

1 0

[JIRA] (OVIRT-1161) Nightly publisher is broken
by Barak Korren (oVirt JIRA) 19 Feb '17

19 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1161?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1161: -------------------------------- Epic Link: OVIRT-403 > Nightly publisher is broken > --------------------------- > > Key: OVIRT-1161 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1161 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > Priority: Highest > > Nightly publisher is currently broken, this has caused some of the oVirt snapshot repos to become empty, which in turn caused OST failures, among others. > The error output from the nightly publisher job is as follows: > {code} > [/usr/local/libexec/releng-tools/scan_for_artifacts.sh] ##### Starting artifacts publishing Sun Feb 19 09:00:01 UTC 2017 > FATAL: We still have files under /home/jenkins/artifacts/ovirt-master-snapshot.ready. Please recheck > FATAL: Failed inside the loop > {code} > This is probably caused by YUM metadata that has been placed in the {{/home/jenkins/artifacts/ovirt-master-snapshot.ready}} by repoman that had been added in OVIRT-1152. > This as also surfaced another issue - if the {{*-snapshot.ready}} directory exists while the nightly publisher job runs (which means the cron job did not finish yet), it will happily move the {{*-snaphot.tmp}} directory into it. What it should do instead is wait a while for it to vanish, and then fail if it does not. -- This message was sent by Atlassian JIRA (v1000.769.1#100032)

1 0

[JIRA] (OVIRT-1161) Nightly publisher is broken
by Barak Korren (oVirt JIRA) 19 Feb '17

19 Feb '17

Barak Korren created OVIRT-1161: ----------------------------------- Summary: Nightly publisher is broken Key: OVIRT-1161 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1161 Project: oVirt - virtualization made easy Issue Type: Bug Components: Repositories Mgmt Reporter: Barak Korren Assignee: infra Priority: Highest Nightly publisher is currently broken, this has caused some of the oVirt snapshot repos to become empty, which in turn caused OST failures, among others. The error output from the nightly publisher job is as follows: {code} [/usr/local/libexec/releng-tools/scan_for_artifacts.sh] ##### Starting artifacts publishing Sun Feb 19 09:00:01 UTC 2017 FATAL: We still have files under /home/jenkins/artifacts/ovirt-master-snapshot.ready. Please recheck FATAL: Failed inside the loop {code} This is probably caused by YUM metadata that has been placed in the {{/home/jenkins/artifacts/ovirt-master-snapshot.ready}} by repoman that had been added in OVIRT-1152. This as also surfaced another issue - if the {{*-snapshot.ready}} directory exists while the nightly publisher job runs (which means the cron job did not finish yet), it will happily move the {{*-snaphot.tmp}} directory into it. What it should do instead is wait a while for it to vanish, and then fail if it does not. -- This message was sent by Atlassian JIRA (v1000.769.1#100032)

1 0

[JIRA] (OVIRT-1154) Make jenkins-whitelist use Gerrit groups
by Barak Korren (oVirt JIRA) 19 Feb '17

19 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1154?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1154: ------------------------------------- We don't want to significantly slow down the CI because of this, a good guideline should be for the whole whitelist matching process to take: # At most 1 network fetch (right not if fetches once via cloning from Gerrit) # At most O\(n) time to search the match, where 'n' is the *number of contributors* as opposed to *number of patches* AFAIK we don't keep lists of contributors anywhere ATM, so we'll probably need to scan patches to see who contributed. We may not be able to practically do this fast enough. We will need to check if Git or Gerrit can do this efficiently for us ahead of time. We also need some proper definition of who is considered a contributor. I don't think that someone with a merged patch ever is a good heuristic, should probably be something like N patches merged in the last M months. > Make jenkins-whitelist use Gerrit groups > ---------------------------------------- > > Key: OVIRT-1154 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1154 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Right now our white list is based on a text file with email addresses in it. Its kinda silly when we already have lists and groups of users in Gerrit. > Some suggestions: > * make any members of a project's "maintainers" group automatically white-listed > * make a specific group for other white-listed people -- This message was sent by Atlassian JIRA (v1000.769.1#100032)

1 0

[JIRA] (OVIRT-1160) Sort search results in Jenkins Manual Trigger
by Barak Korren (oVirt JIRA) 19 Feb '17

19 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1160?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1160: ------------------------------------- Maybe the Gerrit query syntax also supports ordering of the results? > Sort search results in Jenkins Manual Trigger > --------------------------------------------- > > Key: OVIRT-1160 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1160 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Allon Mureinik > Assignee: infra > > When searching for a change in Jenkins Manual Retrigger, the results return in a seemingly random order. > Sorting them by Change Id (or frankly, any logical sorting) would be great, and make this tool easier to use. > [not sure if this can be done with this plugin, but thought I'd ask just in case] > See example of unsorted changes: http://imgur.com/a/JdYQ6 -- This message was sent by Atlassian JIRA (v1000.769.1#100032)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5399 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 18 Feb '17

18 Feb '17

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

1 1

oVirt infra daily report - unstable production jobs - 235
by jenkins＠jenkins.phx.ovirt.org 18 Feb '17

18 Feb '17

------=_Part_215_1287312497.1487458827981 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/235//artifact/exported-a… Cheers, Jenkins ------=_Part_215_1287312497.1487458827981 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 - 18/02/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-live_master_experimental_create-iso-el7-…">ovirt-live_master_experimental_create-iso-el7-x86_64</a> </td><td> <h3>This job generates a nightly iso of ovirt-live using experimental repos</h3> </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-master-experimental_build-…">ovirt-node-ng_ovirt-master-experimental_build-artifacts-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/ovirt-system-tests_master_check-patch-el7-x86_…">ovirt-system-tests_master_check-patch-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/ovirt_4.0_system-tests_stable/">ovirt_4.0_system-tests_stable</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_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_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_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/repos_4.1_check-closure_el7_merged/">repos_4.1_check-closure_el7_merged</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/repos_4.1_check-closure_fc24_merged/">repos_4.1_check-closure_fc24_merged</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/repos_master_check-closure_el7_merged/">repos_master_check-closure_el7_merged</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/repos_master_check-closure_fc24_merged/">repos_master_check-closure_fc24_merged</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_4.0/">test-repo_ovirt_experimental_4.0</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_215_1287312497.1487458827981--

1 0

[JIRA] (OVIRT-1160) Sort search results in Jenkins Manual Trigger
by Allon Mureinik (oVirt JIRA) 18 Feb '17

18 Feb '17

Allon Mureinik created OVIRT-1160: ------------------------------------- Summary: Sort search results in Jenkins Manual Trigger Key: OVIRT-1160 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1160 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Allon Mureinik Assignee: infra When searching for a change in Jenkins Manual Retrigger, the results return in a seemingly random order. Sorting them by Change Id (or frankly, any logical sorting) would be great, and make this tool easier to use. [not sure if this can be done with this plugin, but thought I'd ask just in case] See example of unsorted changes: http://imgur.com/a/JdYQ6 -- This message was sent by Atlassian JIRA (v1000.769.1#100032)

1 0

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

17 Feb '17

------=_Part_209_1376903713.1487372428067 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/234//artifact/exported-a… Cheers, Jenkins ------=_Part_209_1376903713.1487372428067 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/02/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-live_master_experimental_create-iso-el7-…">ovirt-live_master_experimental_create-iso-el7-x86_64</a> </td><td> <h3>This job generates a nightly iso of ovirt-live using experimental repos</h3> </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-master-experimental_build-…">ovirt-node-ng_ovirt-master-experimental_build-artifacts-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/ovirt-system-tests_master_check-patch-el7-x86_…">ovirt-system-tests_master_check-patch-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/ovirt_4.0_system-tests_stable/">ovirt_4.0_system-tests_stable</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_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_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/repos_4.1_check-closure_el7_merged/">repos_4.1_check-closure_el7_merged</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/repos_4.1_check-closure_fc24_merged/">repos_4.1_check-closure_fc24_merged</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/repos_master_check-closure_el7_merged/">repos_master_check-closure_el7_merged</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/repos_master_check-closure_fc24_merged/">repos_master_check-closure_fc24_merged</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_4.0/">test-repo_ovirt_experimental_4.0</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_209_1376903713.1487372428067--

1 0

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

17 Feb '17

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

1 1

[JIRA] (OVIRT-1159) remove stale host ID from PHX HE setup
by Evgheni Dereveanchin (oVirt JIRA) 17 Feb '17

17 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1159?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1159: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > remove stale host ID from PHX HE setup > -------------------------------------- > > Key: OVIRT-1159 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1159 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > Our PHX environment was updated from 3.5 with host reinstalls which left behind a stale host: > ID host > 1 ovirt-srv01 (stale) > 2 ovirt-srv02 > 3 ovirt-srv03 > 4 ovirt-srv01 > Since [BZ#1215437|https://bugzilla.redhat.com/show_bug.cgi?id=1215437] and [BZ#1321889|https://bugzilla.redhat.com/show_bug.cgi?id=1321889] were included in 3.6 it is now possible to fix the stale ID for ovirt-srv01 since it's pending 4.1 upgrades anyway > Action plan: > 1) put ovirt-srv01 in Maintenance > 2) remove from Engine > 3) re-deploy (or just clean HA agent cache?) > 4) run hosted-engine --deploy and re-add with ID=1 > 5) put in Maintenance again, stop HA agent > # service ovirt-ha-agent stop > 6) clean up leftover ID=4: > # hosted-engine --clean-metadata --host-id=4 > 7) start agent, wait for FSM to initialize, activate host > # service ovirt-ha-agent start > Will test it on my test upgraded environment first. -- This message was sent by Atlassian JIRA (v1000.769.0#100032)

1 0

[JIRA] (OVIRT-1159) remove stale host ID from PHX HE setup
by Evgheni Dereveanchin (oVirt JIRA) 17 Feb '17

17 Feb '17

Evgheni Dereveanchin created OVIRT-1159: ------------------------------------------- Summary: remove stale host ID from PHX HE setup Key: OVIRT-1159 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1159 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra Our PHX environment was updated from 3.5 with host reinstalls which left behind a stale host: ID host 1 ovirt-srv01 (stale) 2 ovirt-srv02 3 ovirt-srv03 4 ovirt-srv01 Since [BZ#1215437|https://bugzilla.redhat.com/show_bug.cgi?id=1215437] and [BZ#1321889|https://bugzilla.redhat.com/show_bug.cgi?id=1321889] were included in 3.6 it is now possible to fix the stale ID for ovirt-srv01 since it's pending 4.1 upgrades anyway Action plan: 1) put ovirt-srv01 in Maintenance 2) remove from Engine 3) re-deploy (or just clean HA agent cache?) 4) run hosted-engine --deploy and re-add with ID=1 5) put in Maintenance again, stop HA agent # service ovirt-ha-agent stop 6) clean up leftover ID=4: # hosted-engine --clean-metadata --host-id=4 7) start agent, wait for FSM to initialize, activate host # service ovirt-ha-agent start Will test it on my test upgraded environment first. -- This message was sent by Atlassian JIRA (v1000.769.0#100032)

1 0

[JIRA] (OVIRT-1154) Make jenkins-whitelist use Gerrit groups
by Michal Skrivanek (oVirt JIRA) 17 Feb '17

17 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1154?page=com.atlassian.jira.… ] Michal Skrivanek commented on OVIRT-1154: ----------------------------------------- would be best to use list of contributors rather than only maintainers > Make jenkins-whitelist use Gerrit groups > ---------------------------------------- > > Key: OVIRT-1154 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1154 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Right now our white list is based on a text file with email addresses in it. Its kinda silly when we already have lists and groups of users in Gerrit. > Some suggestions: > * make any members of a project's "maintainers" group automatically white-listed > * make a specific group for other white-listed people -- This message was sent by Atlassian JIRA (v1000.769.0#100032)

1 0

Build failed in Jenkins: deploy-to-ovirt_experimental_4.1 #2127
by jenkins＠jenkins.phx.ovirt.org 17 Feb '17

17 Feb '17

See <http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental_4.1/2127/display/…> ------------------------------------------ [...truncated 3.87 KB...] + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + echo 'Timed out waiting for lock' Timed out waiting for lock + exit 1 Build step 'Execute shell' marked build as failure [ssh-agent] Stopped.

1 1

Build failed in Jenkins: deploy-to-ovirt_experimental_4.0 #5823
by jenkins＠jenkins.phx.ovirt.org 17 Feb '17

17 Feb '17

See <http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental_4.0/5823/display/…> ------------------------------------------ [...truncated 3.87 KB...] + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + echo 'Timed out waiting for lock' Timed out waiting for lock + exit 1 Build step 'Execute shell' marked build as failure [ssh-agent] Stopped.

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5369 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 16 Feb '17

16 Feb '17

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

1 2

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

16 Feb '17

------=_Part_183_1107746628.1487286008483 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/233//artifact/exported-a… Cheers, Jenkins ------=_Part_183_1107746628.1487286008483 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/02/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-live_master_experimental_create-iso-el7-…">ovirt-live_master_experimental_create-iso-el7-x86_64</a> </td><td> <h3>This job generates a nightly iso of ovirt-live using experimental repos</h3> </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-master-experimental_build-…">ovirt-node-ng_ovirt-master-experimental_build-artifacts-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/ovirt-system-tests_master_check-patch-el7-x86_…">ovirt-system-tests_master_check-patch-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/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/repos_4.1_check-closure_el7_merged/">repos_4.1_check-closure_el7_merged</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/repos_4.1_check-closure_fc24_merged/">repos_4.1_check-closure_fc24_merged</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/repos_master_check-closure_el7_merged/">repos_master_check-closure_el7_merged</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/repos_master_check-closure_fc24_merged/">repos_master_check-closure_fc24_merged</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_4.0/">test-repo_ovirt_experimental_4.0</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_4.1_DANIELS_TEST/">test-repo_ovirt_experimental_4.1_DANIELS_TEST</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> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master_DANIELS_TE…">test-repo_ovirt_experimental_master_DANIELS_TEST</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_183_1107746628.1487286008483--

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5367 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 16 Feb '17

16 Feb '17

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

1 1

[JIRA] (OVIRT-1158) PHX engine crashed during live migration
by Evgheni Dereveanchin (oVirt JIRA) 16 Feb '17

16 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1158?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1158: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > PHX engine crashed during live migration > ---------------------------------------- > > Key: OVIRT-1158 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1158 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Hosting > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > Today I tried migrating the 4.1 Engine to upgrade hosts. This caused the VM to fail and be restarted by the HA agent. Need to review logs and confirm what caused this behavior. -- This message was sent by Atlassian JIRA (v1000.766.0#100032)

1 0

[JIRA] (OVIRT-1158) PHX engine crashed during live migration
by Evgheni Dereveanchin (oVirt JIRA) 16 Feb '17

16 Feb '17

Evgheni Dereveanchin created OVIRT-1158: ------------------------------------------- Summary: PHX engine crashed during live migration Key: OVIRT-1158 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1158 Project: oVirt - virtualization made easy Issue Type: Bug Components: Hosting Reporter: Evgheni Dereveanchin Assignee: infra Today I tried migrating the 4.1 Engine to upgrade hosts. This caused the VM to fail and be restarted by the HA agent. Need to review logs and confirm what caused this behavior. -- This message was sent by Atlassian JIRA (v1000.766.0#100032)

1 0

[JIRA] (OVIRT-1157) Re-factor the standard-CI triggers file
by Barak Korren (oVirt JIRA) 16 Feb '17

16 Feb '17

Barak Korren created OVIRT-1157: ----------------------------------- Summary: Re-factor the standard-CI triggers file Key: OVIRT-1157 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1157 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Reporter: Barak Korren Assignee: infra The {{/jobs/confs/yaml/triggers/standard.yaml}} file contains A LOT of needless code duplication. We need to re-factor it with templates and YAML inheritance. -- This message was sent by Atlassian JIRA (v1000.766.0#100032)

1 0

[JIRA] (OVIRT-1157) Re-factor the standard-CI triggers file
by Barak Korren (oVirt JIRA) 16 Feb '17

16 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1157?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1157: -------------------------------- Epic Link: OVIRT-400 > Re-factor the standard-CI triggers file > --------------------------------------- > > Key: OVIRT-1157 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1157 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > The {{/jobs/confs/yaml/triggers/standard.yaml}} file contains A LOT of needless code duplication. We need to re-factor it with templates and YAML inheritance. -- This message was sent by Atlassian JIRA (v1000.766.0#100032)

1 0

Build failed in Jenkins: deploy-to-ovirt_experimental_4.1 #2114
by jenkins＠jenkins.phx.ovirt.org 16 Feb '17

16 Feb '17

See <http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental_4.1/2114/display/…> ------------------------------------------ [...truncated 3.82 KB...] + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + echo 'Timed out waiting for lock' Timed out waiting for lock + exit 1 Build step 'Execute shell' marked build as failure [ssh-agent] Stopped.

1 1

[Announcement] new manual job for ost
by Daniel Belenky 16 Feb '17

16 Feb '17

Hi all, The oVirt infra team is proud to announce the *new manual job for ovirt-system-tests.* Link: http://jenkins.ovirt.org/job/ovirt-system-tests_manual/ The new job supports a new feature: testing oVirt upgrades! The job can test upgrading current oVirt release from a previous release with various options, see table below for full available testing matrix. The new upgrade jobs will be soon added to the experimental flow and will be part of the gating done to oVirt tested repo ( i.e any rpm which breaks upgrade won't reach the tested repo ). *How to use?* - In order to use the manual ost job, you first have to build RPMs from your open patches. Just add a comment to your open patch and write *'ci please build', *and you'll get a link to the job that builds your patch. - Go to the manual job, and click '*Build with parameters'*. - Choose the oVirt version you wish to test (should match to the oVirt version of your patch). - Choose the suite type from the drop-down menu. The Available options are: - *Basic* - *Upgrade from release* - *Upgrade from prev release* versionprevreleaserelease master 4.0 4.1 4.1 4.0 4.1 4.0 ---- 4.0 - Add your custom URLs: here you should supply the link to the Jenkins job that built your patch. - Choose the fallback repo: This is the repo that the Job will fetch the RPMs from. Your RPMs will be used on top of those RPMs. - Choose Lago version: (Unless you want to test Lago's new features, just use the table version) - Click on *Build*, and let the job run. You'll get all the relevant logs from the suites under the '*Build artifacts*' directory when the job is done. For more detailed review of using the manual job, please refer to Verifying an oVirt patch with ovirt-system-tests <http://ovirt-system-tests.readthedocs.io/en/latest/docs/CI/developers_info.…> . Please feel free to contact the infra team on infra(a)ovirt.org for any more questions you have. Sincerely, *Daniel Belenky* *RHV DevOps* *Red Hat Israel*

2 1

[JIRA] (OVIRT-1156) Fwd: build-artifacts-on-demand marks CI +1
by Barak Korren (oVirt JIRA) 16 Feb '17

16 Feb '17

Barak Korren created OVIRT-1156: ----------------------------------- Summary: Fwd: build-artifacts-on-demand marks CI +1 Key: OVIRT-1156 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1156 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Barak Korren Assignee: infra Forwarding to Jira. ---------- Forwarded message ---------- From: Yedidyah Bar David <didi(a)redhat.com> Date: 16 February 2017 at 15:02 Subject: build-artifacts-on-demand marks CI +1 To: infra <infra(a)ovirt.org> Hi all, I have a change [1] that currently fails some jenkins jobs, so it gets -1 from it. After pushing patchset 4 (a mere rebase actually), I ran build-artifacts-on-demand ("ci please build"), and it passed, and set CI +1. Then I rebased again and again got -1 as expected. IMO build-artifacts-on-demand should not set CI +1, it might be misleading for the maintainer to think that all is good when in fact CI failed. [1] https://gerrit.ovirt.org/71590 -- Didi _______________________________________________ Infra mailing list Infra(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/infra -- Barak Korren bkorren(a)redhat.com RHCE, RHCi, RHV-DevOps Team https://ifireball.wordpress.com/ -- This message was sent by Atlassian JIRA (v1000.766.0#100032)

1 0

build-artifacts-on-demand marks CI +1
by Yedidyah Bar David 16 Feb '17

16 Feb '17

Hi all, I have a change [1] that currently fails some jenkins jobs, so it gets -1 from it. After pushing patchset 4 (a mere rebase actually), I ran build-artifacts-on-demand ("ci please build"), and it passed, and set CI +1. Then I rebased again and again got -1 as expected. IMO build-artifacts-on-demand should not set CI +1, it might be misleading for the maintainer to think that all is good when in fact CI failed. [1] https://gerrit.ovirt.org/71590 -- Didi

2 1

[JIRA] (OVIRT-1155) Please enable https on resources.ovirt.org
by Barak Korren (oVirt JIRA) 16 Feb '17

16 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1155?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1155: -------------------------------- Issue Type: New Feature (was: By-EMAIL) > Please enable https on resources.ovirt.org > ------------------------------------------ > > Key: OVIRT-1155 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1155 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Repositories Mgmt > Reporter: sbonazzo > Assignee: infra > > If no technical issue is preventing us to enable https, please enable it > for resources.ovirt.org. > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.766.0#100032)

1 0

[JIRA] (OVIRT-1155) Please enable https on resources.ovirt.org
by Barak Korren (oVirt JIRA) 16 Feb '17

16 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1155?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1155: -------------------------------- Component/s: Repositories Mgmt > Please enable https on resources.ovirt.org > ------------------------------------------ > > Key: OVIRT-1155 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1155 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: Repositories Mgmt > Reporter: sbonazzo > Assignee: infra > > If no technical issue is preventing us to enable https, please enable it > for resources.ovirt.org. > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.766.0#100032)

1 0

[JIRA] (OVIRT-1155) Please enable https on resources.ovirt.org
by sbonazzo (oVirt JIRA) 16 Feb '17

16 Feb '17

sbonazzo created OVIRT-1155: ------------------------------- Summary: Please enable https on resources.ovirt.org Key: OVIRT-1155 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1155 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra If no technical issue is preventing us to enable https, please enable it for resources.ovirt.org. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.766.0#100032)

1 0

[JIRA] (OVIRT-1154) Make jenkins-whitelist use Gerrit groups
by Barak Korren (oVirt JIRA) 16 Feb '17

16 Feb '17

Barak Korren created OVIRT-1154: ----------------------------------- Summary: Make jenkins-whitelist use Gerrit groups Key: OVIRT-1154 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1154 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Reporter: Barak Korren Assignee: infra Right now our white list is based on a text file with email addresses in it. Its kinda silly when we already have lists and groups of users in Gerrit. Some suggestions: * make any members of a project's "maintainers" group automatically white-listed * make a specific group for other white-listed people -- This message was sent by Atlassian JIRA (v1000.766.0#100032)

1 0

[JIRA] (OVIRT-1154) Make jenkins-whitelist use Gerrit groups
by Barak Korren (oVirt JIRA) 16 Feb '17

16 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1154?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1154: -------------------------------- Epic Link: OVIRT-400 > Make jenkins-whitelist use Gerrit groups > ---------------------------------------- > > Key: OVIRT-1154 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1154 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Right now our white list is based on a text file with email addresses in it. Its kinda silly when we already have lists and groups of users in Gerrit. > Some suggestions: > * make any members of a project's "maintainers" group automatically white-listed > * make a specific group for other white-listed people -- This message was sent by Atlassian JIRA (v1000.766.0#100032)

1 0

[JIRA] (OVIRT-1153) Ensure standard-CI uses the jenkins-whitelist
by Barak Korren (oVirt JIRA) 16 Feb '17

16 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1153?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1153: ----------------------------------- Assignee: Barak Korren (was: infra) > Ensure standard-CI uses the jenkins-whitelist > --------------------------------------------- > > Key: OVIRT-1153 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1153 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Barak Korren > Assignee: Barak Korren > Priority: Highest > > Standard-CI means everyone on the interned can submit a patch with an anutomation script that end up running in oVirt CI. > We want to limit this a little to ensure not anyone can try to hack us. We used to have the jenkins-whitelist repo for that, but it hasn't been used for the standard-CI jobs so far. -- This message was sent by Atlassian JIRA (v1000.766.0#100032)

1 0

[JIRA] (OVIRT-1153) Ensure standard-CI uses the jenkins-whitelist
by Barak Korren (oVirt JIRA) 16 Feb '17

16 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1153?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1153: ------------------------------------- Patch added to integrate whitelist: https://gerrit.ovirt.org/#/c/72402/ Need to also alert developers before merging > Ensure standard-CI uses the jenkins-whitelist > --------------------------------------------- > > Key: OVIRT-1153 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1153 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Priority: Highest > > Standard-CI means everyone on the interned can submit a patch with an anutomation script that end up running in oVirt CI. > We want to limit this a little to ensure not anyone can try to hack us. We used to have the jenkins-whitelist repo for that, but it hasn't been used for the standard-CI jobs so far. -- This message was sent by Atlassian JIRA (v1000.766.0#100032)

1 0

[JIRA] (OVIRT-1103) Please fix ovirt-system-test for 4.1-pre
by eyal edri [Administrator] (oVirt JIRA) 16 Feb '17

16 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1103?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1103: --------------------------------------------- Resolution: Won't Fix Status: Done (was: To Do) There is no need to maintain a job for 4.1-pre since its created only before release. We can utilize the existing manual job to run verification on 'pre' released and choose either 'stable' or 'tested' release as base. Its also possible to test upgrades now as well. http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests… > Please fix ovirt-system-test for 4.1-pre > ---------------------------------------- > > Key: OVIRT-1103 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1103 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Tried to use it for testing 4.1-pre repo with 4.1 async release and fails > on missing packages. > Tried also the manual job specifying both 4.1-pre and 4.1 repos, hoping > this would have fixed the missing packages requirements but it fails again. > Not enough time today for investigating myself. > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.766.0#100032)

1 0

[JIRA] (OVIRT-1105) Re: Need a topic branch for experimental development
by eyal edri [Administrator] (oVirt JIRA) 16 Feb '17

16 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1105?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1105: --------------------------------------------- Resolution: Fixed Status: Done (was: To Do) branched created from master. > Re: Need a topic branch for experimental development > ---------------------------------------------------- > > Key: OVIRT-1105 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1105 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Gil Shinar > Assignee: infra > > Adding infra-support so a ticket will be opened > On Sun, Feb 5, 2017 at 1:17 PM, Roy Golan <rgolan(a)redhat.com> wrote: > > Hi infra, > > > > I want a new gerrit branch that will make it easier to collaborate with > > more developers on experimental, edgy changes. > > > > > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > -- This message was sent by Atlassian JIRA (v1000.766.0#100032)

1 0

[JIRA] (OVIRT-1153) Ensure standard-CI uses the jenkins-whitelist
by Barak Korren (oVirt JIRA) 16 Feb '17

16 Feb '17

Barak Korren created OVIRT-1153: ----------------------------------- Summary: Ensure standard-CI uses the jenkins-whitelist Key: OVIRT-1153 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1153 Project: oVirt - virtualization made easy Issue Type: Bug Components: Jenkins Reporter: Barak Korren Assignee: infra Priority: Highest Standard-CI means everyone on the interned can submit a patch with an anutomation script that end up running in oVirt CI. We want to limit this a little to ensure not anyone can try to hack us. We used to have the jenkins-whitelist repo for that, but it hasn't been used for the standard-CI jobs so far. -- This message was sent by Atlassian JIRA (v1000.766.0#100032)

1 0

[JIRA] (OVIRT-1153) Ensure standard-CI uses the jenkins-whitelist
by Barak Korren (oVirt JIRA) 16 Feb '17

16 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1153?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1153: -------------------------------- Epic Link: OVIRT-400 > Ensure standard-CI uses the jenkins-whitelist > --------------------------------------------- > > Key: OVIRT-1153 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1153 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Priority: Highest > > Standard-CI means everyone on the interned can submit a patch with an anutomation script that end up running in oVirt CI. > We want to limit this a little to ensure not anyone can try to hack us. We used to have the jenkins-whitelist repo for that, but it hasn't been used for the standard-CI jobs so far. -- This message was sent by Atlassian JIRA (v1000.766.0#100032)

1 0

[JIRA] (OVIRT-1093) new gerrit project request: ovirt-on-kubevirt
by eyal edri [Administrator] (oVirt JIRA) 16 Feb '17

16 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1093?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1093: --------------------------------------------- Resolution: Fixed Status: Done (was: To Do) please reopen if anything else is needed > new gerrit project request: ovirt-on-kubevirt > --------------------------------------------- > > Key: OVIRT-1093 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1093 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: Evgheni Dereveanchin > > On Jan 31, 2017 18:13, "Fabian Deutsch" <fdeutsch(a)redhat.com> wrote: > > Hey, > > > > could you please create the following repository on gerrit: > > > > ovirt-on-kubevirt.git > > > > This repository can documentation, diagrams, and a demo of how ovirt > > can consume KubeVirt. > > > > - fabian > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > -- This message was sent by Atlassian JIRA (v1000.766.0#100032)

1 0

[JIRA] (OVIRT-1130) unjustified ci-1 due to ava.io.IOException: Remote call on vm0053.workers-phx.ovirt.org failed
by eyal edri [Administrator] (oVirt JIRA) 16 Feb '17

16 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1130?page=com.atlassian.jira.… ] eyal edri [Administrator] reassigned OVIRT-1130: ------------------------------------------------ Assignee: Evgheni Dereveanchin (was: infra) > unjustified ci-1 due to ava.io.IOException: Remote call on vm0053.workers-phx.ovirt.org failed > ---------------------------------------------------------------------------------------------- > > Key: OVIRT-1130 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1130 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: danken > Assignee: Evgheni Dereveanchin > > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc25-x86_64/1282/conso… -- This message was sent by Atlassian JIRA (v1000.766.0#100032)

1 0

[JIRA] (OVIRT-1137) Please open a new "ovirt-engine-metrics" repository
by eyal edri [Administrator] (oVirt JIRA) 16 Feb '17

16 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1137?page=com.atlassian.jira.… ] eyal edri [Administrator] reassigned OVIRT-1137: ------------------------------------------------ Assignee: Evgheni Dereveanchin (was: infra) > Please open a new "ovirt-engine-metrics" repository > --------------------------------------------------- > > Key: OVIRT-1137 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1137 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Shirly Radco > Assignee: Evgheni Dereveanchin > > Hi, > Please remove ovirt-metrics repo(empty) and replace with > ovirt-engine-metrics. > Maintainer Shirly Radco (sradco) > Sync with Gitub > Description same as in ovirt-metrics repository. > Best regards, > Shirly Radco > BI Software Engineer > Red Hat Israel Ltd. > 34 Jerusalem Road > Building A, 4th floor > Ra'anana, Israel 4350109 -- This message was sent by Atlassian JIRA (v1000.766.0#100032)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_4.0 - Build #3789 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 15 Feb '17

15 Feb '17

------=_Part_158_294378875.1487164629672 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.0/3789/, Build Number: 3789, Build Status: FAILURE ------=_Part_158_294378875.1487164629672--

1 1

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

15 Feb '17

------=_Part_165_1093411030.1487199608940 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/232//artifact/exported-a… Cheers, Jenkins ------=_Part_165_1093411030.1487199608940 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/02/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-live_master_experimental_create-iso-el7-…">ovirt-live_master_experimental_create-iso-el7-x86_64</a> </td><td> <h3>This job generates a nightly iso of ovirt-live using experimental repos</h3> </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-master-experimental_build-…">ovirt-node-ng_ovirt-master-experimental_build-artifacts-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/ovirt_3.6_he-system-tests/">ovirt_3.6_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/repos_4.1_check-closure_el7_merged/">repos_4.1_check-closure_el7_merged</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/repos_4.1_check-closure_fc24_merged/">repos_4.1_check-closure_fc24_merged</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/repos_master_check-closure_el7_merged/">repos_master_check-closure_el7_merged</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/repos_master_check-closure_fc24_merged/">repos_master_check-closure_fc24_merged</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_4.0/">test-repo_ovirt_experimental_4.0</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_4.1_DANIELS_TEST/">test-repo_ovirt_experimental_4.1_DANIELS_TEST</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_DANIELS_TE…">test-repo_ovirt_experimental_master_DANIELS_TEST</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_165_1093411030.1487199608940--

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5335 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 15 Feb '17

15 Feb '17

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

1 1

Build failed in Jenkins: deploy-to-ovirt_experimental_4.1 #2021
by jenkins＠jenkins.phx.ovirt.org 15 Feb '17

15 Feb '17

See <http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental_4.1/2021/display/…> ------------------------------------------ [...truncated 3.83 KB...] + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + sleep 5 + (( i++ )) + (( i < 120 )) + echo 'Timed out waiting for lock' Timed out waiting for lock + exit 1 Build step 'Execute shell' marked build as failure [ssh-agent] Stopped.

1 1

Build failed in Jenkins: ovirt_master_publish-rpms_nightly #454
by jenkins＠jenkins.phx.ovirt.org 15 Feb '17

15 Feb '17

See <http://jenkins.ovirt.org/job/ovirt_master_publish-rpms_nightly/454/display/…> ------------------------------------------ Started by user Barak Korren [EnvInject] - Loading node environment variables. Building on master in workspace <http://jenkins.ovirt.org/job/ovirt_master_publish-rpms_nightly/ws/> [WS-CLEANUP] Deleting project workspace... [workspace] $ /bin/bash -xe /tmp/hudson1956343899944051116.sh + rm -rf <http://jenkins.ovirt.org/job/ovirt_master_publish-rpms_nightly/ws/artifacts> + mkdir <http://jenkins.ovirt.org/job/ovirt_master_publish-rpms_nightly/ws/artifacts> Copied 5 artifacts from "ovirt-host-deploy_master_build-artifacts-el7-x86_64" build number 41 Copied 5 artifacts from "ovirt-host-deploy_master_build-artifacts-fc24-x86_64" build number 31 Copied 5 artifacts from "ovirt-host-deploy_master_build-artifacts-fc25-x86_64" build number 4 Copied 7 artifacts from "otopi_master_build-artifacts-el7-x86_64" build number 42 Copied 7 artifacts from "otopi_master_build-artifacts-fc24-x86_64" build number 29 Copied 7 artifacts from "otopi_master_build-artifacts-fc25-x86_64" build number 5 Copied 5 artifacts from "ovirt-vmconsole_master_build-artifacts-el7-x86_64" build number 2 Copied 6 artifacts from "ovirt-vmconsole_master_build-artifacts-fc24-x86_64" build number 1 Copied 5 artifacts from "ovirt-vmconsole_master_build-artifacts-fc25-x86_64" build number 1 Copied 10 artifacts from "ovirt-imageio_master_build-artifacts-el7-x86_64" build number 71 Copied 10 artifacts from "ovirt-imageio_master_build-artifacts-fc24-x86_64" build number 34 Copied 10 artifacts from "ovirt-imageio_master_build-artifacts-fc25-x86_64" build number 5 Copied 4 artifacts from "ovirt-iso-uploader_master_build-artifacts-el7-x86_64" build number 9 Copied 4 artifacts from "ovirt-iso-uploader_master_build-artifacts-fc24-x86_64" build number 5 Copied 3 artifacts from "ovirt-iso-uploader_master_build-artifacts-fc25-x86_64" build number 1 Copied 3 artifacts from "ovirt-log-collector_master_build-artifacts-el7-x86_64" build number 10 Copied 3 artifacts from "ovirt-log-collector_master_build-artifacts-fc24-x86_64" build number 6 Copied 3 artifacts from "ovirt-log-collector_master_build-artifacts-fc25-x86_64" build number 1 Copied 3 artifacts from "ovirt-engine-cli_master_build-artifacts-el7-x86_64" build number 2 Copied 3 artifacts from "ovirt-engine-cli_master_build-artifacts-fc24-x86_64" build number 2 Copied 3 artifacts from "ovirt-engine-cli_master_build-artifacts-fc25-x86_64" build number 1 Copied 3 artifacts from "ovirt-engine-extension-aaa-jdbc_master_build-artifacts-el7-x86_64" build number 5 Copied 3 artifacts from "ovirt-engine-extension-aaa-jdbc_master_build-artifacts-fc24-x86_64" build number 5 Copied 3 artifacts from "ovirt-engine-extension-aaa-jdbc_master_build-artifacts-fc25-x86_64" build number 5 Copied 4 artifacts from "ovirt-engine-extension-aaa-ldap_master_build-artifacts-el7-x86_64" build number 5 Copied 4 artifacts from "ovirt-engine-extension-aaa-ldap_master_build-artifacts-fc24-x86_64" build number 5 Copied 4 artifacts from "ovirt-engine-extension-aaa-ldap_master_build-artifacts-fc25-x86_64" build number 4 Copied 3 artifacts from "ovirt-engine-extension-aaa-misc_master_build-artifacts-el7-x86_64" build number 1 Copied 3 artifacts from "ovirt-engine-extension-aaa-misc_master_build-artifacts-fc24-x86_64" build number 1 Copied 3 artifacts from "ovirt-engine-extension-aaa-misc_master_build-artifacts-fc25-x86_64" build number 1 Copied 3 artifacts from "ovirt-engine-extension-logger-log4j_master_build-artifacts-el7-x86_64" build number 3 Copied 3 artifacts from "ovirt-engine-extension-logger-log4j_master_build-artifacts-fc24-x86_64" build number 3 Copied 3 artifacts from "ovirt-engine-extension-logger-log4j_master_build-artifacts-fc25-x86_64" build number 3 Copied 4 artifacts from "ovirt-dwh_master_build-artifacts-el7-x86_64" build number 36 Copied 4 artifacts from "ovirt-dwh_master_build-artifacts-fc24-x86_64" build number 16 Copied 4 artifacts from "ovirt-dwh_master_build-artifacts-fc25-x86_64" build number 1 Copied 3 artifacts from "ovirt-setup-lib_master_build-artifacts-el7-x86_64" build number 12 Copied 3 artifacts from "ovirt-setup-lib_master_build-artifacts-fc24-x86_64" build number 8 Copied 3 artifacts from "ovirt-setup-lib_master_build-artifacts-fc25-x86_64" build number 1 Copied 4 artifacts from "vdsm-jsonrpc-java_master_build-artifacts-el7-x86_64" build number 61 Copied 4 artifacts from "vdsm-jsonrpc-java_master_build-artifacts-fc24-x86_64" build number 40 Copied 4 artifacts from "vdsm-jsonrpc-java_master_build-artifacts-fc25-x86_64" build number 4 Copied 3 artifacts from "ovirt-engine-sdk_master_build-artifacts-el7-x86_64" build number 101 Copied 5 artifacts from "ovirt-engine-sdk_master_build-artifacts-fc24-x86_64" build number 76 Copied 3 artifacts from "ovirt-engine-sdk_master_build-artifacts-fc25-x86_64" build number 1 Copied 4 artifacts from "python-ovirt-engine-sdk4_master_build-artifacts-el7-x86_64" build number 34 Copied 5 artifacts from "python-ovirt-engine-sdk4_master_build-artifacts-fc24-x86_64" build number 34 Copied 5 artifacts from "python-ovirt-engine-sdk4_master_build-artifacts-fc25-x86_64" build number 10 Copied 4 artifacts from "ovirt-engine-sdk_master_build-artifacts-el7-ppc64le" build number 56 Copied 5 artifacts from "ovirt-engine-sdk_master_build-artifacts-fc24-ppc64le" build number 56 Copied 5 artifacts from "ovirt-engine-sdk_master_build-artifacts-fc25-ppc64le" build number 9 Copied 4 artifacts from "ovirt-engine-sdk-java_master_build-artifacts-el7-x86_64" build number 76 Copied 4 artifacts from "ovirt-engine-sdk-java_master_build-artifacts-fc24-x86_64" build number 56 Copied 4 artifacts from "ovirt-engine-sdk-java_master_build-artifacts-fc25-x86_64" build number 3 Copied 3 artifacts from "java-ovirt-engine-sdk4_master_build-artifacts-el7-x86_64" build number 16 Copied 3 artifacts from "java-ovirt-engine-sdk4_master_build-artifacts-fc24-x86_64" build number 19 ERROR: Unable to find a build for artifact copy from: java-ovirt-engine-sdk4_master_build-artifacts-fc25-x86_64

1 3

Expecting property name enclosed in double quotes (was: Change in ovirt-engine[master]: packaging: spec: Require collectd/fluentd+plugins)
by Yedidyah Bar David 15 Feb '17

15 Feb '17

On Wed, Feb 15, 2017 at 12:48 PM, Code Review <gerrit(a)ovirt.org> wrote: > From Jenkins CI: > > Jenkins CI has posted comments on this change. > > Change subject: packaging: spec: Require collectd/fluentd+plugins > ...................................................................... > > > Patch Set 4: Continuous-Integration-1 > > Build Failed > > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/184… : FAILURE 10:32:28 File "/home/jenkins/workspace/ovirt-engine_master_check-patch-el7-x86_64/ovirt-engine/mocker-epel-7-x86_64.el7.cfg", line 93, in <module> 10:32:28 mirrors_from_http('http://mirrors.phx.ovirt.org/repos/yum/all_latest.json'), 10:32:28 10:32:28 json.decoder.JSONDecodeError: Expecting property name enclosed in double quotes: line 2 column 1 (char 23) > > http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-4.1_el7_creat… : FAILURE > > http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_cr… : FAILURE > > http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-4.0_el7_creat… : FAILURE > > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-fc24-x86_64/12… : SUCCESS > > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-fc25-x86_64/24… : SUCCESS > > -- > To view, visit https://gerrit.ovirt.org/71590 > To unsubscribe, visit https://gerrit.ovirt.org/settings > > Gerrit-MessageType: comment > Gerrit-Change-Id: Ie497bae2d80c7bf27ff4bd401e9c83dc49a33694 > Gerrit-PatchSet: 4 > Gerrit-Project: ovirt-engine > Gerrit-Branch: master > Gerrit-Owner: Yedidyah Bar David <didi(a)redhat.com> > Gerrit-Reviewer: Jenkins CI > Gerrit-Reviewer: Shirly Radco <sradco(a)redhat.com> > Gerrit-Reviewer: Yedidyah Bar David <didi(a)redhat.com> > Gerrit-Reviewer: gerrit-hooks <automation(a)ovirt.org> > Gerrit-HasComments: No -- Didi

3 2

[JIRA] (OVIRT-1149) Add VDSM container build in build-artifacts stage
by eyal edri [Administrator] (oVirt JIRA) 15 Feb '17

15 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1149?page=com.atlassian.jira.… ] eyal edri [Administrator] reassigned OVIRT-1149: ------------------------------------------------ Assignee: Daniel Belenky (was: infra) > Add VDSM container build in build-artifacts stage > ------------------------------------------------- > > Key: OVIRT-1149 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1149 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: Daniel Belenky > Priority: High > > As part of [1], we need to start building VDSM as container and publish it so that OST can consume it and verify it. > This ticket is for tracking progress on VDSM, a similar ticket will be opened for ovirt-engine. > [1] https://ovirt-jira.atlassian.net/browse/OST-39 -- This message was sent by Atlassian JIRA (v1000.747.1#100028)

1 0

[JIRA] (OVIRT-1152) Sync the 'tested' repo into the 'snapshot' repo
by Barak Korren (oVirt JIRA) 15 Feb '17

15 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1152?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1152: ----------------------------------- Assignee: Barak Korren (was: infra) > Sync the 'tested' repo into the 'snapshot' repo > ----------------------------------------------- > > Key: OVIRT-1152 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1152 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: Barak Korren > Priority: High > > As part of the efforts to deprecate the nightly publisher job, and also increase the reliability of published oVirt repos, we've created the 'tested' repo (OVIRT-1045), and started asking developers to use it as a source for package dependencies, and as the main target fur publishing builds. > This situation now is that some packages , that have recently joined the "Standard-CI" effort, do not get published in the 'snapshot' repo. This causes projects that have been relying on the 'snapshot' repo as the exclusive source of dependencies to fail CI. > We want to try to make the move to using OST as the source of published packages (As opposed to the 'nightly publisher' job) transparent to developers and users. For that end we will make the 'nightly publisher' jib cause packages to also be collected from the `tested` repo. Over time we can remove code from the publisher job that collects packages directly. -- This message was sent by Atlassian JIRA (v1000.747.1#100028)

1 0

[JIRA] (OVIRT-1152) Sync the 'tested' repo into the 'snapshot' repo
by Barak Korren (oVirt JIRA) 15 Feb '17

15 Feb '17

Barak Korren created OVIRT-1152: ----------------------------------- Summary: Sync the 'tested' repo into the 'snapshot' repo Key: OVIRT-1152 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1152 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Repositories Mgmt Reporter: Barak Korren Assignee: infra Priority: High As part of the efforts to deprecate the nightly publisher job, and also increase the reliability of published oVirt repos, we've created the 'tested' repo (OVIRT-1045), and started asking developers to use it as a source for package dependencies, and as the main target fur publishing builds. This situation now is that some packages , that have recently joined the "Standard-CI" effort, do not get published in the 'snapshot' repo. This causes projects that have been relying on the 'snapshot' repo as the exclusive source of dependencies to fail CI. We want to try to make the move to using OST as the source of published packages (As opposed to the 'nightly publisher' job) transparent to developers and users. For that end we will make the 'nightly publisher' jib cause packages to also be collected from the `tested` repo. Over time we can remove code from the publisher job that collects packages directly. -- This message was sent by Atlassian JIRA (v1000.747.1#100028)

1 0