May 2017 - Infra - oVirt List Archives

oVirt infra daily report - unstable production jobs - 310
by jenkins＠jenkins.phx.ovirt.org 02 May '17

02 May '17

------=_Part_469_1179392868.1493766005958 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/310//artifact/exported-a… Cheers, Jenkins ------=_Part_469_1179392868.1493766005958 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 - 02/05/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.1_hc-system-tests/">ovirt_4.1_hc-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master-ansible-system-tests/">ovirt_master-ansible-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/">ovirt_master_hc-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_469_1179392868.1493766005958--

1 0

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

02 May '17

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

1 1

[JIRA] (OVIRT-1296) review Rebase Always submit strategy on Gerrit
by Evgheni Dereveanchin (oVirt JIRA) 02 May '17

02 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1296?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1296: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > review Rebase Always submit strategy on Gerrit > ---------------------------------------------- > > Key: OVIRT-1296 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1296 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > Priority: Lowest > > A new submit strategy was included in recent builds of Gerrit: Rebase Always. > [Docs|https://gerrit-review.googlesource.com/Documentation/project-configura…] > {quote}Basically, the same as Rebase If Necessary, but it creates a new patchset even if fast forward is possible AND like Cherry Pick it ensures footers such as Change-Id, Reviewed-On, and others are present in resulting commit that is merged. > Thus, Rebase Always can be considered similar to Cherry Pick, but with the important distinction that Rebase Always does not ignore dependencies.{quote} > It is only available in [2.14|https://gerrit.googlesource.com/gerrit/+/stable-2.14/gerrit-server/src…] while we are still at 2.12 and [2.13|https://gerrit.googlesource.com/gerrit/+/stable-2.13/gerrit-server/src…] is the current stable branch. -- This message was sent by Atlassian JIRA (v1000.929.1#100040)

1 0

3.6 build jobs are not working?
by Martin Perina 02 May '17

02 May '17

Hi, we have patch for 3.6 [1] and all build jobs failed. Looking at the error relevant 3.6 repositories are no longer available at resources.ovirt.org. Does that mean we no longer support 3.6 build jobs in jenkins? If so it's OK to merge a patch even without CI+1? Thanks Martin [1] https://gerrit.ovirt.org/#/c/76290/

3 3

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

01 May '17

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

1 1

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

01 May '17

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

1 0

[JIRA] (OVIRT-1296) review Rebase Always submit strategy on Gerrit
by Barak Korren (oVirt JIRA) 01 May '17

01 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1296?page=com.atlassian.jira.… ] Barak Korren edited comment on OVIRT-1296 at 5/1/17 10:12 PM: -------------------------------------------------------------- We should close this ticket, i don`t think its gonna be useful for anything. Read my comment above. 'Rebase always' is just like 'Rebase when necessary' for all practical purposes, only it guarantees that the commit that ends up being merged will always be different then the one the developer that wrote it has locally. This will just be annoying. was (Author: bkorren(a)redhat.com) We should close this ticket, i don`t think its gonna be useful for anything. Read my comment above. 'Rebase always' is just like 'Rebase when necessary' fir all practical purposes, only it guarantees that the commit that ends up being merged will always be different then the one the developer that wrote it has locally. This will just be annoying. > review Rebase Always submit strategy on Gerrit > ---------------------------------------------- > > Key: OVIRT-1296 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1296 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: Lowest > > A new submit strategy was included in recent builds of Gerrit: Rebase Always. > [Docs|https://gerrit-review.googlesource.com/Documentation/project-configura…] > {quote}Basically, the same as Rebase If Necessary, but it creates a new patchset even if fast forward is possible AND like Cherry Pick it ensures footers such as Change-Id, Reviewed-On, and others are present in resulting commit that is merged. > Thus, Rebase Always can be considered similar to Cherry Pick, but with the important distinction that Rebase Always does not ignore dependencies.{quote} > It is only available in [2.14|https://gerrit.googlesource.com/gerrit/+/stable-2.14/gerrit-server/src…] while we are still at 2.12 and [2.13|https://gerrit.googlesource.com/gerrit/+/stable-2.13/gerrit-server/src…] is the current stable branch. -- This message was sent by Atlassian JIRA (v1000.929.1#100040)

1 0

[JIRA] (OVIRT-1296) review Rebase Always submit strategy on Gerrit
by Barak Korren (oVirt JIRA) 01 May '17

01 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1296?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1296: ------------------------------------- We should close this ticket, i don`t think its gonna be useful for anything. Read my comment above. 'Rebase always' is just like 'Rebase when necessary' fir all practical purposes, only it guarantees that the commit that ends up being merged will always be different then the one the developer that wrote it has locally. This will just be annoying. > review Rebase Always submit strategy on Gerrit > ---------------------------------------------- > > Key: OVIRT-1296 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1296 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: Lowest > > A new submit strategy was included in recent builds of Gerrit: Rebase Always. > [Docs|https://gerrit-review.googlesource.com/Documentation/project-configura…] > {quote}Basically, the same as Rebase If Necessary, but it creates a new patchset even if fast forward is possible AND like Cherry Pick it ensures footers such as Change-Id, Reviewed-On, and others are present in resulting commit that is merged. > Thus, Rebase Always can be considered similar to Cherry Pick, but with the important distinction that Rebase Always does not ignore dependencies.{quote} > It is only available in [2.14|https://gerrit.googlesource.com/gerrit/+/stable-2.14/gerrit-server/src…] while we are still at 2.12 and [2.13|https://gerrit.googlesource.com/gerrit/+/stable-2.13/gerrit-server/src…] is the current stable branch. -- This message was sent by Atlassian JIRA (v1000.929.1#100040)

1 0

[JIRA] (OVIRT-1311) Nightliy publisher 'move_jenkins_nightly' cron job failes when the *.ready dir is empty
by Barak Korren (oVirt JIRA) 01 May '17

01 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1311?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1311: ------------------------------------- We're still using the publisher cron jobs, so still relevant. > Nightliy publisher 'move_jenkins_nightly' cron job failes when the *.ready dir is empty > --------------------------------------------------------------------------------------- > > Key: OVIRT-1311 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1311 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Barak Korren > Assignee: infra > > If The '{{*.ready}}' directory does not contain any RPMs, the cron job fails. This failure causes all repos not to get published until the failure is fixed. -- This message was sent by Atlassian JIRA (v1000.929.1#100040)

1 0

[JIRA] (OVIRT-1356) Fwd: ansible-suite-master failure
by Nadav Goldin (oVirt JIRA) 01 May '17

01 May '17

Nadav Goldin created OVIRT-1356: ----------------------------------- Summary: Fwd: ansible-suite-master failure Key: OVIRT-1356 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1356 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nadav Goldin Assignee: infra +infra-support to open ticket. This is the failure: 10:35:15 TASK [ovirt-deploy : Remove default datacenter] ******************************** 10:35:18 An exception occurred during task execution. To see the full traceback, use -vvv. The error was: TypeError: expected string or buffer 10:35:18 fatal: [lago-ansible-suite-master-engine]: FAILED! => {"changed": false, "failed": true, "msg": "expected string or buffer"} 10:35:18 to retry, use: --limit @/home/jenkins/workspace/ovirt-system-tests_master_check-patch-el7-x86_64/ovirt-system-tests/ansible-suite-master/engine.retry 10:35:18 10:35:18 PLAY RECAP ********************************************************************* Replicated again in: http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_… ---------- Forwarded message ---------- From: Nadav Goldin <ngoldin(a)redhat.com> Date: Sun, Apr 30, 2017 at 7:59 PM Subject: ansible-suite-master failure To: Ondra Machacek <omachace(a)redhat.com> Cc: infra <infra(a)ovirt.org> Hi Ondra, By coincidence when working on a different patch [1] I noticed the ansible suite is failing on the infra side, this should be fixed in [2], but now it is failing[3] on something else: 16:46:27 TASK [ovirt-deploy : Remove default datacenter] ******************************** 16:46:29 An exception occurred during task execution. To see the full traceback, use -vvv. The error was: TypeError: expected string or buffer 16:46:29 fatal: [lago-ansible-suite-master-engine]: FAILED! => {"changed": false, "failed": true, "msg": "expected string or buffer"} 16:46:29 to retry, use: --limit @/home/jenkins/workspace/ovirt-system-tests_master_check-patch-el7-x86_64/ovirt-system-tests/ansible-suite-master/engine.retry 16:46:29 16:46:29 PLAY RECAP ********************************************************************* 16:46:29 lago-ansible-suite-master-engine : ok=14 changed=1 unreachable=0 failed=1 As the none-ansible suite is not failing, I assume this is something on the ansible side, could you please take a look? Thanks, Nadav. [1] https://gerrit.ovirt.org/#/c/76225 [2] https://gerrit.ovirt.org/#/c/76250 [3] http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_… -- This message was sent by Atlassian JIRA (v1000.929.1#100040)

1 0