- Infra - oVirt List Archives

[JIRA] (OVIRT-1162) Make sure cron failure email from resources.ovirt.org reach the infra list
by Barak Korren (oVirt JIRA) 19 Feb '17

19 Feb '17

Barak Korren created OVIRT-1162: ----------------------------------- Summary: Make sure cron failure email from resources.ovirt.org reach the infra list Key: OVIRT-1162 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1162 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Repositories Mgmt Reporter: Barak Korren Assignee: infra Priority: High There are quite a few things that run there with cron and we need to know when they fail. -- 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 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) 18 Feb '17

18 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