- Infra - oVirt List Archives

[JIRA] (OVIRT-824) Jenkins CI not triggering for ovirt-engine-dashboard gerrit patches
by eyal edri [Administrator] (oVirt JIRA) 13 Nov '16

13 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-824?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-824: ------------------------------------------------- [~oourfali(a)redhat.com] this was already resolved, please see previous comments. > Jenkins CI not triggering for ovirt-engine-dashboard gerrit patches > ------------------------------------------------------------------- > > Key: OVIRT-824 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-824 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Scott Dickerson > Assignee: infra > > Hi, > I submitted an ovirt-engine-dashboard patch [1] last night. The > gerrit-hooks ran just fine to attach the patch to its BZ [2]. However, the > normal Jenkins CI hooks/job did not. I tried rerunning the hooks with the > "Rerun-Hooks: all" gerrit comments on the patch, but Jenkins CI did not run > again. How can we tell if the Jenkins CI triggers on the > ovirt-engine-dashboard gerrit are still configured correctly? What can be > done to fix the problem? > To attempt to work around the issue, I tried the gerrit manual trigger page > [3]. Unfortunately my jenkins account (sdickers) does not have the > appropriate permission to the page. My teammate was able to manually > trigger the job and my patch cleared CI (thanks Greg). Who do I need to > ping to get that permission added to my account? > Regards, > Scott > [1] - https://gerrit.ovirt.org/66368 > [2] - https://bugzilla.redhat.com/1389382 > [3] - http://jenkins.ovirt.org/gerrit_manual_trigger/ > -- > Scott Dickerson > Senior Software Engineer > RHEV-M Engineering - UX Team > Red Hat, Inc -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[JIRA] (OVIRT-824) Jenkins CI not triggering for ovirt-engine-dashboard gerrit patches
by Oved Ourfali (oVirt JIRA) 13 Nov '16

13 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-824?page=com.atlassian.jira.p… ] Oved Ourfali commented on OVIRT-824: ------------------------------------ Adding Eyal. Thanks, Oved On Thu, Nov 10, 2016 at 9:27 PM, Scott Dickerson <sdickers(a)redhat.com> wrote: > Hi, > > I submitted an ovirt-engine-dashboard patch [1] last night. The > gerrit-hooks ran just fine to attach the patch to its BZ [2]. However, the > normal Jenkins CI hooks/job did not. I tried rerunning the hooks with the > "Rerun-Hooks: all" gerrit comments on the patch, but Jenkins CI did not run > again. How can we tell if the Jenkins CI triggers on the > ovirt-engine-dashboard gerrit are still configured correctly? What can be > done to fix the problem? > > To attempt to work around the issue, I tried the gerrit manual trigger > page [3]. Unfortunately my jenkins account (sdickers) does not have the > appropriate permission to the page. My teammate was able to manually > trigger the job and my patch cleared CI (thanks Greg). Who do I need to > ping to get that permission added to my account? > > Regards, > Scott > > [1] - https://gerrit.ovirt.org/66368 > [2] - https://bugzilla.redhat.com/1389382 > [3] - http://jenkins.ovirt.org/gerrit_manual_trigger/ > > -- > Scott Dickerson > Senior Software Engineer > RHEV-M Engineering - UX Team > Red Hat, Inc > > Jenkins CI not triggering for ovirt-engine-dashboard gerrit patches > ------------------------------------------------------------------- > > Key: OVIRT-824 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-824 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Scott Dickerson > Assignee: infra > > Hi, > I submitted an ovirt-engine-dashboard patch [1] last night. The > gerrit-hooks ran just fine to attach the patch to its BZ [2]. However, the > normal Jenkins CI hooks/job did not. I tried rerunning the hooks with the > "Rerun-Hooks: all" gerrit comments on the patch, but Jenkins CI did not run > again. How can we tell if the Jenkins CI triggers on the > ovirt-engine-dashboard gerrit are still configured correctly? What can be > done to fix the problem? > To attempt to work around the issue, I tried the gerrit manual trigger page > [3]. Unfortunately my jenkins account (sdickers) does not have the > appropriate permission to the page. My teammate was able to manually > trigger the job and my patch cleared CI (thanks Greg). Who do I need to > ping to get that permission added to my account? > Regards, > Scott > [1] - https://gerrit.ovirt.org/66368 > [2] - https://bugzilla.redhat.com/1389382 > [3] - http://jenkins.ovirt.org/gerrit_manual_trigger/ > -- > Scott Dickerson > Senior Software Engineer > RHEV-M Engineering - UX Team > Red Hat, Inc -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_3.6 - Build #3557 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 13 Nov '16

13 Nov '16

------=_Part_245_946362966.1479012207537 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/3557/, Build Number: 3557, Build Status: FAILURE ------=_Part_245_946362966.1479012207537--

1 6

[JIRA] (OVIRT-831) enable spam filters for lago-devel mailing list
by eyal edri [Administrator] (oVirt JIRA) 13 Nov '16

13 Nov '16

eyal edri [Administrator] created OVIRT-831: ----------------------------------------------- Summary: enable spam filters for lago-devel mailing list Key: OVIRT-831 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-831 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri [Administrator] Assignee: infra Can you check if its possible? I keep getting requests to approve spam mails to lago-devel. -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[JIRA] (OVIRT-831) enable spam filters for lago-devel mailing list
by eyal edri [Administrator] (oVirt JIRA) 13 Nov '16

13 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-831?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-831: -------------------------------------------- Epic Link: OVIRT-403 > enable spam filters for lago-devel mailing list > ----------------------------------------------- > > Key: OVIRT-831 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-831 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > > Can you check if its possible? > I keep getting requests to approve spam mails to lago-devel. -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[JIRA] (OVIRT-825) re: Assistance
by danken (oVirt JIRA) 13 Nov '16

13 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-825?page=com.atlassian.jira.p… ] danken commented on OVIRT-825: ------------------------------ Billy, could you point me to your attempt to discuss this on devel(a)ovirt.org? I could not find any post under your name. A link like http://lists.ovirt.org/pipermail/users/2016-November/043911.html would be most useful. The short answer is that OvS is not yet available, and that we're working hard to make it reach a tech-preview state. To understand about your specific issue, I'll need to hear more details about the failures you see. Let us continue this discussion on the mailing list, please. > re: Assistance > -------------- > > Key: OVIRT-825 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-825 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Billy Boulden > Assignee: infra > Attachments: image002.png > > > Hello, > Having issues installing and configuring OVIRT with the virtual switch. Need to speak with someone > Billy Boulden, C|EH, C|HFI > Systems Engineer > Information Systems Worldwide > A Wholly-Owned Subsidiary of ECS Federal. Inc. > 3865 Wilson Blvd, #600 > Arlington, VA 22203 > Phone: 571-482-4900 x6004 -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[JIRA] (OVIRT-830) Vdsm lost its "Forge Author" permission?
by eyal edri [Administrator] (oVirt JIRA) 13 Nov '16

13 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-830?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-830: ------------------------------------------------- You don't see any security implication with this? any user (even malicious) has the potential to forge the author identity? Shouldn't this be restricted to maintainers of the project? [~sbendavi(a)redhat.com] > Vdsm lost its "Forge Author" permission? > ---------------------------------------- > > Key: OVIRT-830 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-830 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: danken > Assignee: infra > > Until recently, any registered user could take on somebody else's change, > and post a new patchset to it. > It's very useful when someone wants to fix a typo in someone else's > code, or when we need to take on a work of a sick/vacating developer. > Please amend this. I'm not 100% sure, but it could be fix by setting > "Forge Author" on the vdsm project. > https://gerrit-review.googlesource.com/Documentation/access-control.html#ca… -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #3290 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 13 Nov '16

13 Nov '16

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

1 3

[JIRA] (OVIRT-830) Vdsm lost its "Forge Author" permission?
by danken (oVirt JIRA) 13 Nov '16

13 Nov '16

danken created OVIRT-830: ---------------------------- Summary: Vdsm lost its "Forge Author" permission? Key: OVIRT-830 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-830 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: danken Assignee: infra Until recently, any registered user could take on somebody else's change, and post a new patchset to it. It's very useful when someone wants to fix a typo in someone else's code, or when we need to take on a work of a sick/vacating developer. Please amend this. I'm not 100% sure, but it could be fix by setting "Forge Author" on the vdsm project. https://gerrit-review.googlesource.com/Documentation/access-control.html#ca… -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_4.0 - Build #2828 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 13 Nov '16

13 Nov '16

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

1 1

qemu-kvm-ev 2.6 landing on snapshot repos
by Sandro Bonazzola 13 Nov '16

13 Nov '16

Hi, tonight qemu-kvm-ev 2.6 will land in snapshot repositories for master, 4.0 and 3.6. Please note that you'll need RHEL 7.3 or CentOS 7.3 ( currently ON_QA at http://buildlogs.centos.org/c7.1611.00 ) to use it. qemu-kvm-ev 2.3 is still available in those repos and on CentOS Virt SIG. Jenkins jobs may have failures related to this so please be sure to either filter qemu-kvm-ev 2.6 or versionlock it to 2.3 or add CentOS 7.3 testing repo to the job. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

3 7

[oVirt Jenkins] test-repo_ovirt_experimental_3.6 - Build #3555 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 12 Nov '16

12 Nov '16

------=_Part_239_1899021378.1479008137801 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/3555/, Build Number: 3555, Build Status: FAILURE ------=_Part_239_1899021378.1479008137801--

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_3.6 - Build #3551 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 12 Nov '16

12 Nov '16

------=_Part_230_1326453246.1478995993865 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/3551/, Build Number: 3551, Build Status: FAILURE ------=_Part_230_1326453246.1478995993865--

1 3

[oVirt Jenkins] test-repo_ovirt_experimental_3.6 - Build #3546 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 12 Nov '16

12 Nov '16

------=_Part_217_1991764896.1478981653657 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/3546/, Build Number: 3546, Build Status: FAILURE ------=_Part_217_1991764896.1478981653657--

1 4

oVirt infra daily report - unstable production jobs - 136
by jenkins＠jenkins.phx.ovirt.org 12 Nov '16

12 Nov '16

------=_Part_226_2126974700.1478991607783 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/136//artifact/exported-a… Cheers, Jenkins ------=_Part_226_2126974700.1478991607783 Content-Type: application/octet-stream; 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 - 12/11/2016 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Jobs (Production)</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/cockpit-ovirt_ovirt-4.1_build-artifacts-fc23-x…">cockpit-ovirt_ovirt-4.1_build-artifacts-fc23-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/fabric-ovirt_master_check-merged-el7-x86_64/">fabric-ovirt_master_check-merged-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-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_master_build-artifacts-el7-x86_6…">ovirt-node-ng_master_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-node-ng_ovirt-4.0-pre_build-artifacts-el…">ovirt-node-ng_ovirt-4.0-pre_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-node-ng_ovirt-4.0_build-artifacts-el7-x8…">ovirt-node-ng_ovirt-4.0_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-release_master_build-artifacts-all-x86_6…">ovirt-release_master_build-artifacts-all-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/ovirt_3.6_image-ng-system-tests/">ovirt_3.6_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_3.6_system-tests/">ovirt_3.6_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/qemu_3.6_create-rpms-el7-ppc64le_merged/">qemu_3.6_create-rpms-el7-ppc64le_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/qemu_4.0_create-rpms-el7-ppc64le_merged/">qemu_4.0_create-rpms-el7-ppc64le_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/qemu_master_create-rpms-el7-ppc64le_merged/">qemu_master_create-rpms-el7-ppc64le_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/repoman_master_check-merged-el6-x86_64/">repoman_master_check-merged-el6-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/repoman_master_check-merged-el7-x86_64/">repoman_master_check-merged-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/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_3.6/">test-repo_ovirt_experimental_3.6</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/vdsm_master_build-artifacts-fc24-ppc64le/">vdsm_master_build-artifacts-fc24-ppc64le</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/vdsm_master_build-artifacts-fc24-x86_64/">vdsm_master_build-artifacts-fc24-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> ------=_Part_226_2126974700.1478991607783--

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_3.6 - Build #3541 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 12 Nov '16

12 Nov '16

------=_Part_205_298649205.1478967235001 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/3541/, Build Number: 3541, Build Status: FAILURE ------=_Part_205_298649205.1478967235001--

1 4

[oVirt Jenkins] test-repo_ovirt_experimental_3.6 - Build #3536 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 12 Nov '16

12 Nov '16

------=_Part_196_159052096.1478953546206 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/3536/, Build Number: 3536, Build Status: FAILURE ------=_Part_196_159052096.1478953546206--

1 3

[JIRA] (OVIRT-829) 26531 infra-support
by m.kos＠lycos.com (oVirt JIRA) 12 Nov '16

12 Nov '16

m.kos(a)lycos.com created OVIRT-829: ------------------------------------- Summary: 26531 infra-support Key: OVIRT-829 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-829 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: m.kos(a)lycos.com Assignee: infra Attachments: MESSAGE_1194292623_infra-support.zip -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_3.6 - Build #3529 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 12 Nov '16

12 Nov '16

------=_Part_176_417653450.1478936127917 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/3529/, Build Number: 3529, Build Status: FAILURE ------=_Part_176_417653450.1478936127917--

1 6

[JIRA] (OVIRT-824) Jenkins CI not triggering for ovirt-engine-dashboard gerrit patches
by eyal edri [Administrator] (oVirt JIRA) 12 Nov '16

12 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-824?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-824: -------------------------------------------- Resolution: Fixed Status: Done (was: To Do) > Jenkins CI not triggering for ovirt-engine-dashboard gerrit patches > ------------------------------------------------------------------- > > Key: OVIRT-824 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-824 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Scott Dickerson > Assignee: infra > > Hi, > I submitted an ovirt-engine-dashboard patch [1] last night. The > gerrit-hooks ran just fine to attach the patch to its BZ [2]. However, the > normal Jenkins CI hooks/job did not. I tried rerunning the hooks with the > "Rerun-Hooks: all" gerrit comments on the patch, but Jenkins CI did not run > again. How can we tell if the Jenkins CI triggers on the > ovirt-engine-dashboard gerrit are still configured correctly? What can be > done to fix the problem? > To attempt to work around the issue, I tried the gerrit manual trigger page > [3]. Unfortunately my jenkins account (sdickers) does not have the > appropriate permission to the page. My teammate was able to manually > trigger the job and my patch cleared CI (thanks Greg). Who do I need to > ping to get that permission added to my account? > Regards, > Scott > [1] - https://gerrit.ovirt.org/66368 > [2] - https://bugzilla.redhat.com/1389382 > [3] - http://jenkins.ovirt.org/gerrit_manual_trigger/ > -- > Scott Dickerson > Senior Software Engineer > RHEV-M Engineering - UX Team > Red Hat, Inc -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[JIRA] (OVIRT-828) ovirt-engine_master_check-patch-fc24-x86_64 failing
by eyal edri [Administrator] (oVirt JIRA) 12 Nov '16

12 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-828?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-828: ------------------------------------------------- Actually its not related, it seems that the job is looking for fc24 dir under ovirt-4.0-snapshot-static dir and it wasn't there. It might have been caused by recent work to move out of fc23 which will be EOL soon, anyway, i've created the new dir and added one rpm there, not sure which ones are needed. [~sbonazolla(a)redhat.com] do you know if we need any specific RPMs for fc24 in ovirt-4.0-snapshot-static? > ovirt-engine_master_check-patch-fc24-x86_64 failing > --------------------------------------------------- > > Key: OVIRT-828 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-828 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-fc24-x86_64/68… > Doesn't appear related to the patch. > > > > 17:52:04 Finish: cleaning yum metadata > > 17:52:04 Mock Version: 1.2.21 > > 17:52:04 INFO: Mock Version: 1.2.21 > > 17:52:04 Start: yum install > > 17:52:09 ERROR: Command failed. See logs for output. > > 17:52:09 # /usr/bin/yum-deprecated --installroot > > /var/lib/mock/fedora-24-x86_64-a84bda050a5e85bcae66e67894bf5f93-17376/root/ > > --releasever 24 install @buildsys-build --setopt=tsflags=nocontexts > > 17:52:09 Init took 6 seconds > Thanks, > Greg > -- > Greg Sheremeta, MBA > Red Hat, Inc. > Sr. Software Engineer > gshereme(a)redhat.com -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[JIRA] (OVIRT-828) ovirt-engine_master_check-patch-fc24-x86_64 failing
by eyal edri [Administrator] (oVirt JIRA) 12 Nov '16

12 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-828?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-828: ------------------------------------------------- bin', 'SHELL': '/bin/bash', 'PS1': '<mock-chroot> \\s-\\v\\$ ', 'LD_PRELOAD': '/tmp/tmpuh9e19lk/$LIB/nosync.so', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'TERM': 'vt100', 'LC_MESSAGES': 'C', 'HOME': '/builddir', 'LANG': 'en_US.UTF-8'} and shell False DEBUG util.py:421: Yum command has been deprecated, use dnf instead. DEBUG util.py:421: See 'man dnf' and 'man yum2dnf' for more information. DEBUG util.py:421: http://resources.ovirt.org/pub/ovirt-4.0-snapshot-static/rpm/fc24/repodata/…: [Errno 14] HTTP Error 404 - Not Found DEBUG util.py:421: Trying other mirror. DEBUG util.py:421: One of the configured repositories failed ("Custom ovirt-snapshot-static"), DEBUG util.py:421: and yum doesn't have enough cached data to continue. At this point the only DEBUG util.py:421: safe thing yum can do is fail. There are a few ways to work "fix" this: DEBUG util.py:421: 1. Contact the upstream for the repository and get them to fix the problem. DEBUG util.py:421: 2. Reconfigure the baseurl/etc. for the repository, to point to a working DEBUG util.py:421: upstream. This is most often useful if you are using a newer DEBUG util.py:421: distribution release than is supported by the repository (and the DEBUG util.py:421: packages for the previous distribution release still work). DEBUG util.py:421: 3. Disable the repository, so yum won't use it by default. Yum will then DEBUG util.py:421: just ignore the repository until you permanently enable it again or use DEBUG util.py:421: --enablerepo for temporary usage: DEBUG util.py:421: yum-config-manager --disable ovirt-snapshot-static DEBUG util.py:421: 4. Configure the failing repository to be skipped, if it is unavailable. DEBUG util.py:421: Note that yum will try to contact the repo. when it runs most commands, DEBUG util.py:421: so will have to try and fail each time (and thus. yum will be be much DEBUG util.py:421: slower). If it is a very temporary problem though, this is often a nice DEBUG util.py:421: compromise: DEBUG util.py:421: yum-config-manager --save --setopt=ovirt-snapshot-static.skip_if_unavailable=true DEBUG util.py:421: failure: repodata/repomd.xml from ovirt We've had some DDOS attacks recently on our repository and we're looking into ways to handle with it, but it might take some time, Unfortunately for now the best option is just to retrigger the patch, I see http://resources.ovirt.org/pub/ is up and accessible now. > ovirt-engine_master_check-patch-fc24-x86_64 failing > --------------------------------------------------- > > Key: OVIRT-828 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-828 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-fc24-x86_64/68… > Doesn't appear related to the patch. > > > > 17:52:04 Finish: cleaning yum metadata > > 17:52:04 Mock Version: 1.2.21 > > 17:52:04 INFO: Mock Version: 1.2.21 > > 17:52:04 Start: yum install > > 17:52:09 ERROR: Command failed. See logs for output. > > 17:52:09 # /usr/bin/yum-deprecated --installroot > > /var/lib/mock/fedora-24-x86_64-a84bda050a5e85bcae66e67894bf5f93-17376/root/ > > --releasever 24 install @buildsys-build --setopt=tsflags=nocontexts > > 17:52:09 Init took 6 seconds > Thanks, > Greg > -- > Greg Sheremeta, MBA > Red Hat, Inc. > Sr. Software Engineer > gshereme(a)redhat.com -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #3267 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 12 Nov '16

12 Nov '16

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

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_3.6 - Build #3527 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 12 Nov '16

12 Nov '16

------=_Part_170_569394813.1478931316544 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/3527/, Build Number: 3527, Build Status: FAILURE ------=_Part_170_569394813.1478931316544--

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_3.6 - Build #3521 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 11 Nov '16

11 Nov '16

------=_Part_160_224954873.1478917313787 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/3521/, Build Number: 3521, Build Status: FAILURE ------=_Part_160_224954873.1478917313787--

1 4

[oVirt Jenkins] test-repo_ovirt_experimental_3.6 - Build #3518 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 11 Nov '16

11 Nov '16

------=_Part_153_1810021056.1478909634864 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/3518/, Build Number: 3518, Build Status: FAILURE ------=_Part_153_1810021056.1478909634864--

1 2

oVirt infra daily report - unstable production jobs - 135
by jenkins＠jenkins.phx.ovirt.org 11 Nov '16

11 Nov '16

------=_Part_151_554893328.1478905208797 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/135//artifact/exported-a… Cheers, Jenkins ------=_Part_151_554893328.1478905208797 Content-Type: application/octet-stream; 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 - 11/11/2016 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Jobs (Production)</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/cockpit-ovirt_ovirt-4.1_build-artifacts-fc23-x…">cockpit-ovirt_ovirt-4.1_build-artifacts-fc23-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/fabric-ovirt_master_check-merged-el7-x86_64/">fabric-ovirt_master_check-merged-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-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_master_build-artifacts-el7-x86_6…">ovirt-node-ng_master_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-node-ng_ovirt-4.0-pre_build-artifacts-el…">ovirt-node-ng_ovirt-4.0-pre_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-release_master_build-artifacts-all-x86_6…">ovirt-release_master_build-artifacts-all-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/ovirt_3.6_image-ng-system-tests/">ovirt_3.6_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/qemu_3.6_create-rpms-el7-ppc64le_merged/">qemu_3.6_create-rpms-el7-ppc64le_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/qemu_4.0_create-rpms-el7-ppc64le_merged/">qemu_4.0_create-rpms-el7-ppc64le_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/qemu_master_create-rpms-el7-ppc64le_merged/">qemu_master_create-rpms-el7-ppc64le_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/repoman_master_check-merged-el6-x86_64/">repoman_master_check-merged-el6-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/repoman_master_check-merged-el7-x86_64/">repoman_master_check-merged-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/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/vdsm_master_build-artifacts-fc24-ppc64le/">vdsm_master_build-artifacts-fc24-ppc64le</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/vdsm_master_build-artifacts-fc24-x86_64/">vdsm_master_build-artifacts-fc24-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> ------=_Part_151_554893328.1478905208797--

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #3256 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 11 Nov '16

11 Nov '16

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

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_3.6 - Build #3513 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 11 Nov '16

11 Nov '16

------=_Part_143_396031219.1478896988767 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/3513/, Build Number: 3513, Build Status: FAILURE ------=_Part_143_396031219.1478896988767--

1 1

Build failed in Jenkins: ovirt_3.6_system-tests #731
by jenkins＠jenkins.phx.ovirt.org 11 Nov '16

11 Nov '16

See <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/731/changes> Changes: [Yaniv Kaul] Fixes for HE suite ------------------------------------------ [...truncated 752 lines...] ## took 2084 seconds ## rc = 1 ########################################################## ##! ERROR vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv ##! Last 20 log entries: logs/mocker-epel-7-x86_64.el7.basic_suite_3.6.sh/basic_suite_3.6.sh.log ##! + env_cleanup + echo '#########################' ######################### + local res=0 + local uuid + echo '======== Cleaning up' ======== Cleaning up + [[ -e <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/d…> ]] + echo '----------- Cleaning with lago' ----------- Cleaning with lago + lago --workdir <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/d…> destroy --yes --all-prefixes + echo '----------- Cleaning with lago done' ----------- Cleaning with lago done + [[ 0 != \0 ]] + echo '======== Cleanup done' ======== Cleanup done + exit 0 + exit Took 1945 seconds =================================== ##! ##! ERROR ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ##!######################################################## ########################################################## Build step 'Execute shell' marked build as failure Performing Post build task... Match found for :.* : True Logical operation result is TRUE Running script : #!/bin/bash -xe echo 'shell_scripts/system_tests.collect_logs.sh' # # Required jjb vars: # version # VERSION=3.6 SUITE_TYPE= WORKSPACE="$PWD" OVIRT_SUITE="$SUITE_TYPE_suite_$VERSION" TESTS_LOGS="$WORKSPACE/ovirt-system-tests/exported-artifacts" rm -rf "$WORKSPACE/exported-artifacts" mkdir -p "$WORKSPACE/exported-artifacts" if [[ -d "$TESTS_LOGS" ]]; then mv "$TESTS_LOGS/"* "$WORKSPACE/exported-artifacts/" fi [ovirt_3.6_system-tests] $ /bin/bash -xe /tmp/hudson8970629053756507258.sh + echo shell_scripts/system_tests.collect_logs.sh shell_scripts/system_tests.collect_logs.sh + VERSION=3.6 + SUITE_TYPE= + WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/> + OVIRT_SUITE=3.6 + TESTS_LOGS=<http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/e…> + rm -rf <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/731/artifact/exported-a…> + mkdir -p <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/731/artifact/exported-a…> + [[ -d <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/e…> ]] + mv <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/e…> <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/e…> <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/e…> <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/e…> <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/731/artifact/exported-a…> POST BUILD TASK : SUCCESS END OF POST BUILD TASK : 0 Match found for :.* : True Logical operation result is TRUE Running script : #!/bin/bash -xe echo "shell-scripts/mock_cleanup.sh" shopt -s nullglob WORKSPACE="$PWD" # Make clear this is the cleanup, helps reading the jenkins logs cat <<EOC _______________________________________________________________________ ####################################################################### # # # CLEANUP # # # ####################################################################### EOC # Archive the logs, we want them anyway logs=( ./*log ./*/logs ) if [[ "$logs" ]]; then tar cvzf exported-artifacts/logs.tgz "${logs[@]}" rm -rf "${logs[@]}" fi # stop any processes running inside the chroot failed=false mock_confs=("$WORKSPACE"/*/mocker*) # Clean current jobs mockroot if any for mock_conf_file in "${mock_confs[@]}"; do [[ "$mock_conf_file" ]] || continue echo "Cleaning up mock $mock_conf" mock_root="${mock_conf_file##*/}" mock_root="${mock_root%.*}" my_mock="/usr/bin/mock" my_mock+=" --configdir=${mock_conf_file%/*}" my_mock+=" --root=${mock_root}" my_mock+=" --resultdir=$WORKSPACE" #TODO: investigate why mock --clean fails to umount certain dirs sometimes, #so we can use it instead of manually doing all this. echo "Killing all mock orphan processes, if any." $my_mock \ --orphanskill \ || { echo "ERROR: Failed to kill orphans on $chroot." failed=true } mock_root="$(\ grep \ -Po "(?<=config_opts\['root'\] = ')[^']*" \ "$mock_conf_file" \ )" || : [[ "$mock_root" ]] || continue mounts=($(mount | awk '{print $3}' | grep "$mock_root")) || : if [[ "$mounts" ]]; then echo "Found mounted dirs inside the chroot $chroot. Trying to umount." fi for mount in "${mounts[@]}"; do sudo umount --lazy "$mount" \ || { echo "ERROR: Failed to umount $mount." failed=true } done done # Clean any leftover chroot from other jobs for mock_root in /var/lib/mock/*; do this_chroot_failed=false mounts=($(mount | awk '{print $3}' | grep "$mock_root")) || : if [[ "$mounts" ]]; then echo "Found mounted dirs inside the chroot $mock_root." \ "Trying to umount." fi for mount in "${mounts[@]}"; do sudo umount --lazy "$mount" \ || { echo "ERROR: Failed to umount $mount." failed=true this_chroot_failed=true } done if ! $this_chroot_failed; then sudo rm -rf "$mock_root" fi done if $failed; then echo "Aborting." exit 1 fi # remove mock system cache, we will setup proxies to do the caching and this # takes lots of space between runs shopt -u nullglob sudo rm -Rf /var/cache/mock/* # restore the permissions in the working dir, as sometimes it leaves files # owned by root and then the 'cleanup workspace' from jenkins job fails to # clean and breaks the jobs sudo chown -R "$USER" "$WORKSPACE" [ovirt_3.6_system-tests] $ /bin/bash -xe /tmp/hudson4353051331767779201.sh + echo shell-scripts/mock_cleanup.sh shell-scripts/mock_cleanup.sh + shopt -s nullglob + WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/> + cat _______________________________________________________________________ ####################################################################### # # # CLEANUP # # # ####################################################################### + logs=(./*log ./*/logs) + [[ -n ./ovirt-system-tests/logs ]] + tar cvzf exported-artifacts/logs.tgz ./ovirt-system-tests/logs ./ovirt-system-tests/logs/ ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.install_packages/ ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.install_packages/state.log ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.install_packages/build.log ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.install_packages/stdout_stderr.log ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.install_packages/root.log ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.init/ ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.init/state.log ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.init/build.log ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.init/stdout_stderr.log ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.init/root.log ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.clean_rpmdb/ ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.clean_rpmdb/stdout_stderr.log ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.basic_suite_3.6.sh/ ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.basic_suite_3.6.sh/basic_suite_3.6.sh.log + rm -rf ./ovirt-system-tests/logs + failed=false + mock_confs=("$WORKSPACE"/*/mocker*) + for mock_conf_file in '"${mock_confs[@]}"' + [[ -n <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/m…> ]] + echo 'Cleaning up mock ' Cleaning up mock + mock_root=mocker-epel-7-x86_64.el7.cfg + mock_root=mocker-epel-7-x86_64.el7 + my_mock=/usr/bin/mock + my_mock+=' --configdir=<http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests'> + my_mock+=' --root=mocker-epel-7-x86_64.el7' + my_mock+=' --resultdir=<http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/'> + echo 'Killing all mock orphan processes, if any.' Killing all mock orphan processes, if any. + /usr/bin/mock --configdir=<http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests> --root=mocker-epel-7-x86_64.el7 --resultdir=<http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/> --orphanskill WARNING: Could not find required logging config file: <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/l….> Using default... INFO: mock.py version 1.2.21 starting (python version = 3.4.3)... Start: init plugins INFO: selinux enabled Finish: init plugins Start: run Finish: run ++ grep -Po '(?<=config_opts\['\''root'\''\] = '\'')[^'\'']*' <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/m…> + mock_root=epel-7-x86_64-235bec7d0621e95d1cae73d7cf9dc27c + [[ -n epel-7-x86_64-235bec7d0621e95d1cae73d7cf9dc27c ]] + mounts=($(mount | awk '{print $3}' | grep "$mock_root")) ++ mount ++ awk '{print $3}' ++ grep epel-7-x86_64-235bec7d0621e95d1cae73d7cf9dc27c + : + [[ -n '' ]] + false + shopt -u nullglob + sudo rm -Rf /var/cache/mock/epel-7-x86_64-235bec7d0621e95d1cae73d7cf9dc27c + sudo chown -R jenkins <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/> POST BUILD TASK : SUCCESS END OF POST BUILD TASK : 1 Recording test results Archiving artifacts

1 1

[JIRA] (OVIRT-828) ovirt-engine_master_check-patch-fc24-x86_64 failing
by Greg Sheremeta (oVirt JIRA) 11 Nov '16

11 Nov '16

Greg Sheremeta created OVIRT-828: ------------------------------------ Summary: ovirt-engine_master_check-patch-fc24-x86_64 failing Key: OVIRT-828 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-828 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Greg Sheremeta Assignee: infra http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-fc24-x86_64/68… Doesn't appear related to the patch. > > 17:52:04 Finish: cleaning yum metadata > 17:52:04 Mock Version: 1.2.21 > 17:52:04 INFO: Mock Version: 1.2.21 > 17:52:04 Start: yum install > 17:52:09 ERROR: Command failed. See logs for output. > 17:52:09 # /usr/bin/yum-deprecated --installroot > /var/lib/mock/fedora-24-x86_64-a84bda050a5e85bcae66e67894bf5f93-17376/root/ > --releasever 24 install @buildsys-build --setopt=tsflags=nocontexts > 17:52:09 Init took 6 seconds Thanks, Greg -- Greg Sheremeta, MBA Red Hat, Inc. Sr. Software Engineer gshereme(a)redhat.com -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_3.6 - Build #3509 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 11 Nov '16

11 Nov '16

------=_Part_137_759499606.1478888066509 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/3509/, Build Number: 3509, Build Status: FAILURE ------=_Part_137_759499606.1478888066509--

1 1

[JIRA] (OVIRT-824) Jenkins CI not triggering for ovirt-engine-dashboard gerrit patches
by Scott Dickerson (oVirt JIRA) 11 Nov '16

11 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-824?page=com.atlassian.jira.p… ] Scott Dickerson commented on OVIRT-824: --------------------------------------- I just pushed a new update on the patch. Jenkins CI started up the builds at the same time as the gerrit-hooks. Hopefully you did something to make it start working. Otherwise, I'll give credit to the moon phase in relationship to solar flare activity. ;-) > Jenkins CI not triggering for ovirt-engine-dashboard gerrit patches > ------------------------------------------------------------------- > > Key: OVIRT-824 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-824 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Scott Dickerson > Assignee: infra > > Hi, > I submitted an ovirt-engine-dashboard patch [1] last night. The > gerrit-hooks ran just fine to attach the patch to its BZ [2]. However, the > normal Jenkins CI hooks/job did not. I tried rerunning the hooks with the > "Rerun-Hooks: all" gerrit comments on the patch, but Jenkins CI did not run > again. How can we tell if the Jenkins CI triggers on the > ovirt-engine-dashboard gerrit are still configured correctly? What can be > done to fix the problem? > To attempt to work around the issue, I tried the gerrit manual trigger page > [3]. Unfortunately my jenkins account (sdickers) does not have the > appropriate permission to the page. My teammate was able to manually > trigger the job and my patch cleared CI (thanks Greg). Who do I need to > ping to get that permission added to my account? > Regards, > Scott > [1] - https://gerrit.ovirt.org/66368 > [2] - https://bugzilla.redhat.com/1389382 > [3] - http://jenkins.ovirt.org/gerrit_manual_trigger/ > -- > Scott Dickerson > Senior Software Engineer > RHEV-M Engineering - UX Team > Red Hat, Inc -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_3.6 - Build #3506 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 11 Nov '16

11 Nov '16

------=_Part_131_1130264919.1478880909911 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/3506/, Build Number: 3506, Build Status: FAILURE ------=_Part_131_1130264919.1478880909911--

1 1

Build failed in Jenkins: ovirt_4.0_he-system-tests #503
by jenkins＠jenkins.phx.ovirt.org 11 Nov '16

11 Nov '16

See <http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/503/changes> Changes: [Yaniv Kaul] Fixes for HE suite ------------------------------------------ [...truncated 1042 lines...] ## rc = 1 ########################################################## ##! ERROR vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv ##! Last 20 log entries: logs/mocker-epel-7-x86_64.el7.he_basic_suite_4.0.sh/he_basic_suite_4.0.sh.log ##! + env_cleanup + echo '#########################' ######################### + local res=0 + local uuid + echo '======== Cleaning up' ======== Cleaning up + [[ -e <http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-test…> ]] + echo '----------- Cleaning with lago' ----------- Cleaning with lago + lago --workdir <http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-test…> destroy --yes --all-prefixes + echo '----------- Cleaning with lago done' ----------- Cleaning with lago done + [[ 0 != \0 ]] + echo '======== Cleanup done' ======== Cleanup done + exit 0 + exit Took 6969 seconds =================================== ##! ##! ERROR ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ##!######################################################## ########################################################## Build step 'Execute shell' marked build as failure Performing Post build task... Match found for :.* : True Logical operation result is TRUE Running script : #!/bin/bash -xe echo 'shell_scripts/system_tests.collect_logs.sh' # # Required jjb vars: # version # VERSION=4.0 SUITE_TYPE= WORKSPACE="$PWD" OVIRT_SUITE="$SUITE_TYPE_suite_$VERSION" TESTS_LOGS="$WORKSPACE/ovirt-system-tests/exported-artifacts" rm -rf "$WORKSPACE/exported-artifacts" mkdir -p "$WORKSPACE/exported-artifacts" if [[ -d "$TESTS_LOGS" ]]; then mv "$TESTS_LOGS/"* "$WORKSPACE/exported-artifacts/" fi [ovirt_4.0_he-system-tests] $ /bin/bash -xe /tmp/hudson2944217724885758579.sh + echo shell_scripts/system_tests.collect_logs.sh shell_scripts/system_tests.collect_logs.sh + VERSION=4.0 + SUITE_TYPE= + WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/> + OVIRT_SUITE=4.0 + TESTS_LOGS=<http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-test…> + rm -rf <http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/503/artifact/exporte…> + mkdir -p <http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/503/artifact/exporte…> + [[ -d <http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-test…> ]] + mv <http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-test…> <http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/503/artifact/exporte…> POST BUILD TASK : SUCCESS END OF POST BUILD TASK : 0 Match found for :.* : True Logical operation result is TRUE Running script : #!/bin/bash -xe echo "shell-scripts/mock_cleanup.sh" shopt -s nullglob WORKSPACE="$PWD" # Make clear this is the cleanup, helps reading the jenkins logs cat <<EOC _______________________________________________________________________ ####################################################################### # # # CLEANUP # # # ####################################################################### EOC # Archive the logs, we want them anyway logs=( ./*log ./*/logs ) if [[ "$logs" ]]; then tar cvzf exported-artifacts/logs.tgz "${logs[@]}" rm -rf "${logs[@]}" fi # stop any processes running inside the chroot failed=false mock_confs=("$WORKSPACE"/*/mocker*) # Clean current jobs mockroot if any for mock_conf_file in "${mock_confs[@]}"; do [[ "$mock_conf_file" ]] || continue echo "Cleaning up mock $mock_conf" mock_root="${mock_conf_file##*/}" mock_root="${mock_root%.*}" my_mock="/usr/bin/mock" my_mock+=" --configdir=${mock_conf_file%/*}" my_mock+=" --root=${mock_root}" my_mock+=" --resultdir=$WORKSPACE" #TODO: investigate why mock --clean fails to umount certain dirs sometimes, #so we can use it instead of manually doing all this. echo "Killing all mock orphan processes, if any." $my_mock \ --orphanskill \ || { echo "ERROR: Failed to kill orphans on $chroot." failed=true } mock_root="$(\ grep \ -Po "(?<=config_opts\['root'\] = ')[^']*" \ "$mock_conf_file" \ )" || : [[ "$mock_root" ]] || continue mounts=($(mount | awk '{print $3}' | grep "$mock_root")) || : if [[ "$mounts" ]]; then echo "Found mounted dirs inside the chroot $chroot. Trying to umount." fi for mount in "${mounts[@]}"; do sudo umount --lazy "$mount" \ || { echo "ERROR: Failed to umount $mount." failed=true } done done # Clean any leftover chroot from other jobs for mock_root in /var/lib/mock/*; do this_chroot_failed=false mounts=($(mount | awk '{print $3}' | grep "$mock_root")) || : if [[ "$mounts" ]]; then echo "Found mounted dirs inside the chroot $mock_root." \ "Trying to umount." fi for mount in "${mounts[@]}"; do sudo umount --lazy "$mount" \ || { echo "ERROR: Failed to umount $mount." failed=true this_chroot_failed=true } done if ! $this_chroot_failed; then sudo rm -rf "$mock_root" fi done if $failed; then echo "Aborting." exit 1 fi # remove mock system cache, we will setup proxies to do the caching and this # takes lots of space between runs shopt -u nullglob sudo rm -Rf /var/cache/mock/* # restore the permissions in the working dir, as sometimes it leaves files # owned by root and then the 'cleanup workspace' from jenkins job fails to # clean and breaks the jobs sudo chown -R "$USER" "$WORKSPACE" [ovirt_4.0_he-system-tests] $ /bin/bash -xe /tmp/hudson889247978207290418.sh + echo shell-scripts/mock_cleanup.sh shell-scripts/mock_cleanup.sh + shopt -s nullglob + WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/> + cat _______________________________________________________________________ ####################################################################### # # # CLEANUP # # # ####################################################################### + logs=(./*log ./*/logs) + [[ -n ./ovirt-system-tests/logs ]] + tar cvzf exported-artifacts/logs.tgz ./ovirt-system-tests/logs ./ovirt-system-tests/logs/ ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.init/ ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.init/stdout_stderr.log ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.init/state.log ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.init/build.log ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.init/root.log ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.install_packages/ ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.install_packages/stdout_stderr.log ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.install_packages/state.log ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.install_packages/build.log ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.install_packages/root.log ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.clean_rpmdb/ ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.clean_rpmdb/stdout_stderr.log ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.he_basic_suite_4.0.sh/ ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.he_basic_suite_4.0.sh/he_basic_suite_4.0.sh.log + rm -rf ./ovirt-system-tests/logs + failed=false + mock_confs=("$WORKSPACE"/*/mocker*) + for mock_conf_file in '"${mock_confs[@]}"' + [[ -n <http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-test…> ]] + echo 'Cleaning up mock ' Cleaning up mock + mock_root=mocker-epel-7-x86_64.el7.cfg + mock_root=mocker-epel-7-x86_64.el7 + my_mock=/usr/bin/mock + my_mock+=' --configdir=<http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-tests'> + my_mock+=' --root=mocker-epel-7-x86_64.el7' + my_mock+=' --resultdir=<http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/'> + echo 'Killing all mock orphan processes, if any.' Killing all mock orphan processes, if any. + /usr/bin/mock --configdir=<http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-tests> --root=mocker-epel-7-x86_64.el7 --resultdir=<http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/> --orphanskill WARNING: Could not find required logging config file: <http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-test….> Using default... INFO: mock.py version 1.2.21 starting (python version = 3.5.1)... Start: init plugins INFO: selinux enabled Finish: init plugins Start: run Finish: run ++ grep -Po '(?<=config_opts\['\''root'\''\] = '\'')[^'\'']*' <http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-test…> + mock_root=epel-7-x86_64-0c362156a2fa4a935ea8b988eb73b2ad + [[ -n epel-7-x86_64-0c362156a2fa4a935ea8b988eb73b2ad ]] + mounts=($(mount | awk '{print $3}' | grep "$mock_root")) ++ mount ++ awk '{print $3}' ++ grep epel-7-x86_64-0c362156a2fa4a935ea8b988eb73b2ad + : + [[ -n '' ]] + false + shopt -u nullglob + sudo rm -Rf /var/cache/mock/epel-7-x86_64-0c362156a2fa4a935ea8b988eb73b2ad + sudo chown -R jenkins <http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/> POST BUILD TASK : SUCCESS END OF POST BUILD TASK : 1 Recording test results ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? Archiving artifacts

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_3.6 - Build #3500 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 11 Nov '16

11 Nov '16

------=_Part_111_193065631.1478864582023 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/3500/, Build Number: 3500, Build Status: FAILURE ------=_Part_111_193065631.1478864582023--

1 5

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #3244 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 11 Nov '16

11 Nov '16

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

1 1

Build failed in Jenkins: ovirt_3.6_system-tests #728
by jenkins＠jenkins.phx.ovirt.org 11 Nov '16

11 Nov '16

See <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/728/changes> Changes: [Yaniv Kaul] Fixes for HE suite [Eyal Edri] reveting back image tests to use fc23 chroot ------------------------------------------ [...truncated 759 lines...] ## took 1718 seconds ## rc = 1 ########################################################## ##! ERROR vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv ##! Last 20 log entries: logs/mocker-epel-7-x86_64.el7.basic_suite_3.6.sh/basic_suite_3.6.sh.log ##! + env_cleanup + echo '#########################' ######################### + local res=0 + local uuid + echo '======== Cleaning up' ======== Cleaning up + [[ -e <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/d…> ]] + echo '----------- Cleaning with lago' ----------- Cleaning with lago + lago --workdir <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/d…> destroy --yes --all-prefixes + echo '----------- Cleaning with lago done' ----------- Cleaning with lago done + [[ 0 != \0 ]] + echo '======== Cleanup done' ======== Cleanup done + exit 0 + exit Took 1573 seconds =================================== ##! ##! ERROR ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ##!######################################################## ########################################################## Build step 'Execute shell' marked build as failure Performing Post build task... Match found for :.* : True Logical operation result is TRUE Running script : #!/bin/bash -xe echo 'shell_scripts/system_tests.collect_logs.sh' # # Required jjb vars: # version # VERSION=3.6 SUITE_TYPE= WORKSPACE="$PWD" OVIRT_SUITE="$SUITE_TYPE_suite_$VERSION" TESTS_LOGS="$WORKSPACE/ovirt-system-tests/exported-artifacts" rm -rf "$WORKSPACE/exported-artifacts" mkdir -p "$WORKSPACE/exported-artifacts" if [[ -d "$TESTS_LOGS" ]]; then mv "$TESTS_LOGS/"* "$WORKSPACE/exported-artifacts/" fi [ovirt_3.6_system-tests] $ /bin/bash -xe /tmp/hudson7926479753821764354.sh + echo shell_scripts/system_tests.collect_logs.sh shell_scripts/system_tests.collect_logs.sh + VERSION=3.6 + SUITE_TYPE= + WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/> + OVIRT_SUITE=3.6 + TESTS_LOGS=<http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/e…> + rm -rf <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/728/artifact/exported-a…> + mkdir -p <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/728/artifact/exported-a…> + [[ -d <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/e…> ]] + mv <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/e…> <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/e…> <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/e…> <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/e…> <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/728/artifact/exported-a…> POST BUILD TASK : SUCCESS END OF POST BUILD TASK : 0 Match found for :.* : True Logical operation result is TRUE Running script : #!/bin/bash -xe echo "shell-scripts/mock_cleanup.sh" shopt -s nullglob WORKSPACE="$PWD" # Make clear this is the cleanup, helps reading the jenkins logs cat <<EOC _______________________________________________________________________ ####################################################################### # # # CLEANUP # # # ####################################################################### EOC # Archive the logs, we want them anyway logs=( ./*log ./*/logs ) if [[ "$logs" ]]; then tar cvzf exported-artifacts/logs.tgz "${logs[@]}" rm -rf "${logs[@]}" fi # stop any processes running inside the chroot failed=false mock_confs=("$WORKSPACE"/*/mocker*) # Clean current jobs mockroot if any for mock_conf_file in "${mock_confs[@]}"; do [[ "$mock_conf_file" ]] || continue echo "Cleaning up mock $mock_conf" mock_root="${mock_conf_file##*/}" mock_root="${mock_root%.*}" my_mock="/usr/bin/mock" my_mock+=" --configdir=${mock_conf_file%/*}" my_mock+=" --root=${mock_root}" my_mock+=" --resultdir=$WORKSPACE" #TODO: investigate why mock --clean fails to umount certain dirs sometimes, #so we can use it instead of manually doing all this. echo "Killing all mock orphan processes, if any." $my_mock \ --orphanskill \ || { echo "ERROR: Failed to kill orphans on $chroot." failed=true } mock_root="$(\ grep \ -Po "(?<=config_opts\['root'\] = ')[^']*" \ "$mock_conf_file" \ )" || : [[ "$mock_root" ]] || continue mounts=($(mount | awk '{print $3}' | grep "$mock_root")) || : if [[ "$mounts" ]]; then echo "Found mounted dirs inside the chroot $chroot. Trying to umount." fi for mount in "${mounts[@]}"; do sudo umount --lazy "$mount" \ || { echo "ERROR: Failed to umount $mount." failed=true } done done # Clean any leftover chroot from other jobs for mock_root in /var/lib/mock/*; do this_chroot_failed=false mounts=($(mount | awk '{print $3}' | grep "$mock_root")) || : if [[ "$mounts" ]]; then echo "Found mounted dirs inside the chroot $mock_root." \ "Trying to umount." fi for mount in "${mounts[@]}"; do sudo umount --lazy "$mount" \ || { echo "ERROR: Failed to umount $mount." failed=true this_chroot_failed=true } done if ! $this_chroot_failed; then sudo rm -rf "$mock_root" fi done if $failed; then echo "Aborting." exit 1 fi # remove mock system cache, we will setup proxies to do the caching and this # takes lots of space between runs shopt -u nullglob sudo rm -Rf /var/cache/mock/* # restore the permissions in the working dir, as sometimes it leaves files # owned by root and then the 'cleanup workspace' from jenkins job fails to # clean and breaks the jobs sudo chown -R "$USER" "$WORKSPACE" [ovirt_3.6_system-tests] $ /bin/bash -xe /tmp/hudson2018457343601087004.sh + echo shell-scripts/mock_cleanup.sh shell-scripts/mock_cleanup.sh + shopt -s nullglob + WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/> + cat _______________________________________________________________________ ####################################################################### # # # CLEANUP # # # ####################################################################### + logs=(./*log ./*/logs) + [[ -n ./ovirt-system-tests/logs ]] + tar cvzf exported-artifacts/logs.tgz ./ovirt-system-tests/logs ./ovirt-system-tests/logs/ ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.init/ ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.init/stdout_stderr.log ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.init/state.log ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.init/build.log ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.init/root.log ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.install_packages/ ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.install_packages/stdout_stderr.log ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.install_packages/state.log ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.install_packages/build.log ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.install_packages/root.log ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.clean_rpmdb/ ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.clean_rpmdb/stdout_stderr.log ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.basic_suite_3.6.sh/ ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.basic_suite_3.6.sh/basic_suite_3.6.sh.log + rm -rf ./ovirt-system-tests/logs + failed=false + mock_confs=("$WORKSPACE"/*/mocker*) + for mock_conf_file in '"${mock_confs[@]}"' + [[ -n <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/m…> ]] + echo 'Cleaning up mock ' Cleaning up mock + mock_root=mocker-epel-7-x86_64.el7.cfg + mock_root=mocker-epel-7-x86_64.el7 + my_mock=/usr/bin/mock + my_mock+=' --configdir=<http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests'> + my_mock+=' --root=mocker-epel-7-x86_64.el7' + my_mock+=' --resultdir=<http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/'> + echo 'Killing all mock orphan processes, if any.' Killing all mock orphan processes, if any. + /usr/bin/mock --configdir=<http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests> --root=mocker-epel-7-x86_64.el7 --resultdir=<http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/> --orphanskill WARNING: Could not find required logging config file: <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/l….> Using default... INFO: mock.py version 1.2.21 starting (python version = 3.5.1)... Start: init plugins INFO: selinux enabled Finish: init plugins Start: run Finish: run ++ grep -Po '(?<=config_opts\['\''root'\''\] = '\'')[^'\'']*' <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/m…> + mock_root=epel-7-x86_64-235bec7d0621e95d1cae73d7cf9dc27c + [[ -n epel-7-x86_64-235bec7d0621e95d1cae73d7cf9dc27c ]] + mounts=($(mount | awk '{print $3}' | grep "$mock_root")) ++ mount ++ awk '{print $3}' ++ grep epel-7-x86_64-235bec7d0621e95d1cae73d7cf9dc27c + : + [[ -n '' ]] + false + shopt -u nullglob + sudo rm -Rf /var/cache/mock/epel-7-x86_64-235bec7d0621e95d1cae73d7cf9dc27c + sudo chown -R jenkins <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/> POST BUILD TASK : SUCCESS END OF POST BUILD TASK : 1 Recording test results Archiving artifacts

1 2

[oVirt Jenkins] test-repo_ovirt_experimental_3.6 - Build #3498 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 11 Nov '16

11 Nov '16

------=_Part_107_833113289.1478859246070 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/3498/, Build Number: 3498, Build Status: FAILURE ------=_Part_107_833113289.1478859246070--

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #3239 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 11 Nov '16

11 Nov '16

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

1 1

[JIRA] (OVIRT-827) el6 proxy issues
by sbonazzo (oVirt JIRA) 11 Nov '16

11 Nov '16

sbonazzo created OVIRT-827: ------------------------------ Summary: el6 proxy issues Key: OVIRT-827 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-827 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra 3.6 el6 nightly builder is failing downloading rpms, looks like a proxy issue: http://jenkins.ovirt.org/job/ovirt-engine_3.6_build-artifacts-el6-x86_64/15… DEBUG util.py:421: http://proxy.phx.ovirt.org:5000/centos-updates/6/x86_64/Packages/python-lib…: [Errno 14] curl#18 - "transfer closed with 5563146 bytes remaining to read" DEBUG util.py:421: Trying other mirror. DEBUG util.py:421: http://proxy.phx.ovirt.org:5000/centos-updates/6/x86_64/Packages/tzdata-201…: [Errno 14] curl#18 - "transfer closed with 435320 bytes remaining to read" DEBUG util.py:421: Trying other mirror. DEBUG util.py:421: Error downloading packages: DEBUG util.py:421: python-libs-2.6.6-66.el6_8.x86_64: [Errno 256] No more mirrors to try. DEBUG util.py:421: tzdata-2016h-1.el6.noarch: [Errno 256] No more mirrors to try. -- 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.526.2#100018)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_3.6 - Build #3493 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 11 Nov '16

11 Nov '16

------=_Part_96_336814618.1478838143325 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/3493/, Build Number: 3493, Build Status: FAILURE ------=_Part_96_336814618.1478838143325--

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_3.6 - Build #3489 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 10 Nov '16

10 Nov '16

------=_Part_86_1126356185.1478823735706 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/3489/, Build Number: 3489, Build Status: FAILURE ------=_Part_86_1126356185.1478823735706--

1 3

[JIRA] (OVIRT-826) We could not deliver your parcel, #0000733054
by FedEx Ground (oVirt JIRA) 10 Nov '16

10 Nov '16

FedEx Ground created OVIRT-826: ---------------------------------- Summary: We could not deliver your parcel, #0000733054 Key: OVIRT-826 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-826 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: FedEx Ground Assignee: infra Attachments: Label_0000733054.zip Dear Customer, This is to confirm that one or more of your parcels has been shipped. You can review complete details of your order in the find attached. Yours sincerely, Franklin Dougherty, Station Manager. -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

oVirt infra daily report - unstable production jobs - 134
by jenkins＠jenkins.phx.ovirt.org 10 Nov '16

10 Nov '16

------=_Part_83_1104739515.1478818808933 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/134//artifact/exported-a… Cheers, Jenkins ------=_Part_83_1104739515.1478818808933 Content-Type: application/octet-stream; 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 - 10/11/2016 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Jobs (Production)</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/cockpit-ovirt_ovirt-4.1_build-artifacts-fc23-x…">cockpit-ovirt_ovirt-4.1_build-artifacts-fc23-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/fabric-ovirt_master_check-merged-el7-x86_64/">fabric-ovirt_master_check-merged-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-engine_3.6_build-artifacts-el6-x86_64/">ovirt-engine_3.6_build-artifacts-el6-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-node-ng_master_build-artifacts-el7-x86_6…">ovirt-node-ng_master_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-release_master_build-artifacts-all-x86_6…">ovirt-release_master_build-artifacts-all-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/ovirt_3.6_image-ng-system-tests/">ovirt_3.6_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_3.6_system-tests/">ovirt_3.6_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.0_image-ng-system-tests/">ovirt_4.0_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/qemu_3.6_create-rpms-el7-ppc64le_merged/">qemu_3.6_create-rpms-el7-ppc64le_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/qemu_4.0_create-rpms-el7-ppc64le_merged/">qemu_4.0_create-rpms-el7-ppc64le_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/qemu_master_create-rpms-el7-ppc64le_merged/">qemu_master_create-rpms-el7-ppc64le_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/repoman_master_check-merged-el6-x86_64/">repoman_master_check-merged-el6-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/repoman_master_check-merged-el7-x86_64/">repoman_master_check-merged-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/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/vdsm_master_build-artifacts-fc24-ppc64le/">vdsm_master_build-artifacts-fc24-ppc64le</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/vdsm_master_build-artifacts-fc24-x86_64/">vdsm_master_build-artifacts-fc24-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> ------=_Part_83_1104739515.1478818808933--

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #3225 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 10 Nov '16

10 Nov '16

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

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_3.6 - Build #3484 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 10 Nov '16

10 Nov '16

------=_Part_73_684228836.1478809262229 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/3484/, Build Number: 3484, Build Status: FAILURE ------=_Part_73_684228836.1478809262229--

1 1

[JIRA] (OVIRT-825) re: Assistance
by Billy Boulden (oVirt JIRA) 10 Nov '16

10 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-825?page=com.atlassian.jira.p… ] Billy Boulden updated OVIRT-825: -------------------------------- Attachment: image002.png We’ve tried that. I need to speak to someone that has set this up before please From: eyal edri [Administrator] (oVirt JIRA) [mailto:jira@ovirt-jira.atlassian.net] Sent: Thursday, November 10, 2016 3:23 PM To: Billy Boulden <Billy.Boulden(a)ecs-federal.com> Subject: [JIRA] (OVIRT-825) re: Assistance [cid:image001.png@01D23B6A.66003EF0] eyal edri [Administrator]<https://ovirt-jira.atlassian.net/secure/ViewProfile.jspa?name=eedri> commented on [By-EMAIL] OVIRT-825<https://ovirt-jira.atlassian.net/browse/OVIRT-825> Re: re: Assistance<https://ovirt-jira.atlassian.net/browse/OVIRT-825> Hi! You've reached the oVirt infrastructure jira, your best place to get help with oVirt will be on the users list users(a)ovirt.org<mailto:users@ovirt.org> or on the devel list: devel(a)ovirt.org<mailto:devel@ovirt.org>. Its almost weekend for most developers, but you might get an answer as early as tomorrow, if not then on by Sunday. cc danken<https://ovirt-jira.atlassian.net/secure/ViewProfile.jspa?name=danken%40redh…> [Add Comment]<https://ovirt-jira.atlassian.net/browse/OVIRT-825#add-comment> Add Comment<https://ovirt-jira.atlassian.net/browse/OVIRT-825#add-comment> This message was sent by Atlassian JIRA (v1000.526.2#100018-sha1:d415428) [Atlassian logo] > re: Assistance > -------------- > > Key: OVIRT-825 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-825 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Billy Boulden > Assignee: infra > Attachments: image002.png > > > Hello, > Having issues installing and configuring OVIRT with the virtual switch. Need to speak with someone > Billy Boulden, C|EH, C|HFI > Systems Engineer > Information Systems Worldwide > A Wholly-Owned Subsidiary of ECS Federal. Inc. > 3865 Wilson Blvd, #600 > Arlington, VA 22203 > Phone: 571-482-4900 x6004 -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[JIRA] (OVIRT-824) Jenkins CI not triggering for ovirt-engine-dashboard gerrit patches
by Scott Dickerson (oVirt JIRA) 10 Nov '16

10 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-824?page=com.atlassian.jira.p… ] Scott Dickerson commented on OVIRT-824: --------------------------------------- Those 2 were triggered manually by [~gshereme(a)redhat.com] On that patch at 11:39AM (or equivalent in your timezone), I triggered the hooks. You can see the BZ update task run, but not the typical Jenkins CI. Patch 65925 [1], that submitted on Oct 31, shows the Jenkins CI tasks at the same time as the BZ updating one. [1] - https://gerrit.ovirt.org/#/c/65925/ > Jenkins CI not triggering for ovirt-engine-dashboard gerrit patches > ------------------------------------------------------------------- > > Key: OVIRT-824 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-824 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Scott Dickerson > Assignee: infra > > Hi, > I submitted an ovirt-engine-dashboard patch [1] last night. The > gerrit-hooks ran just fine to attach the patch to its BZ [2]. However, the > normal Jenkins CI hooks/job did not. I tried rerunning the hooks with the > "Rerun-Hooks: all" gerrit comments on the patch, but Jenkins CI did not run > again. How can we tell if the Jenkins CI triggers on the > ovirt-engine-dashboard gerrit are still configured correctly? What can be > done to fix the problem? > To attempt to work around the issue, I tried the gerrit manual trigger page > [3]. Unfortunately my jenkins account (sdickers) does not have the > appropriate permission to the page. My teammate was able to manually > trigger the job and my patch cleared CI (thanks Greg). Who do I need to > ping to get that permission added to my account? > Regards, > Scott > [1] - https://gerrit.ovirt.org/66368 > [2] - https://bugzilla.redhat.com/1389382 > [3] - http://jenkins.ovirt.org/gerrit_manual_trigger/ > -- > Scott Dickerson > Senior Software Engineer > RHEV-M Engineering - UX Team > Red Hat, Inc -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[JIRA] (OVIRT-824) Jenkins CI not triggering for ovirt-engine-dashboard gerrit patches
by Greg Sheremeta (oVirt JIRA) 10 Nov '16

10 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-824?page=com.atlassian.jira.p… ] Greg Sheremeta commented on OVIRT-824: -------------------------------------- ^ what he said. "Manually triggered by user gshereme for Gerrit: https://gerrit.ovirt.org/66368" > Jenkins CI not triggering for ovirt-engine-dashboard gerrit patches > ------------------------------------------------------------------- > > Key: OVIRT-824 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-824 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Scott Dickerson > Assignee: infra > > Hi, > I submitted an ovirt-engine-dashboard patch [1] last night. The > gerrit-hooks ran just fine to attach the patch to its BZ [2]. However, the > normal Jenkins CI hooks/job did not. I tried rerunning the hooks with the > "Rerun-Hooks: all" gerrit comments on the patch, but Jenkins CI did not run > again. How can we tell if the Jenkins CI triggers on the > ovirt-engine-dashboard gerrit are still configured correctly? What can be > done to fix the problem? > To attempt to work around the issue, I tried the gerrit manual trigger page > [3]. Unfortunately my jenkins account (sdickers) does not have the > appropriate permission to the page. My teammate was able to manually > trigger the job and my patch cleared CI (thanks Greg). Who do I need to > ping to get that permission added to my account? > Regards, > Scott > [1] - https://gerrit.ovirt.org/66368 > [2] - https://bugzilla.redhat.com/1389382 > [3] - http://jenkins.ovirt.org/gerrit_manual_trigger/ > -- > Scott Dickerson > Senior Software Engineer > RHEV-M Engineering - UX Team > Red Hat, Inc -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0