- Infra - oVirt List Archives

Build failed in Jenkins: ovirt_3.6_publish-rpms_nightly #115
by jenkins＠jenkins.phx.ovirt.org 14 Jul '16

14 Jul '16

See <http://jenkins.ovirt.org/job/ovirt_3.6_publish-rpms_nightly/115/> ------------------------------------------ Started by user Sandro Bonazzola Building on master in workspace <http://jenkins.ovirt.org/job/ovirt_3.6_publish-rpms_nightly/ws/> [WS-CLEANUP] Deleting project workspace... [workspace] $ /bin/bash -xe /tmp/hudson3329493458284527249.sh + rm -rf <http://jenkins.ovirt.org/job/ovirt_3.6_publish-rpms_nightly/ws/artifacts> + mkdir <http://jenkins.ovirt.org/job/ovirt_3.6_publish-rpms_nightly/ws/artifacts> Copied 8 artifacts from "ovirt-host-deploy_3.6_create-rpms-el6-x86_64_merged" build number 2 Copied 10 artifacts from "ovirt-host-deploy_3.6_create-rpms-el7-x86_64_merged" build number 1 Copied 10 artifacts from "ovirt-host-deploy_3.6_create-rpms-fc22-x86_64_merged" build number 1 Copied 10 artifacts from "ovirt-host-deploy_3.6_create-rpms-fc23-x86_64_merged" build number 1 Copied 4 artifacts from "ovirt-engine-sdk_3.6_build-artifacts-el6-x86_64" build number 10 Copied 4 artifacts from "ovirt-engine-sdk_3.6_build-artifacts-el7-x86_64" build number 12 Copied 4 artifacts from "ovirt-engine-sdk_3.6_build-artifacts-fc22-x86_64" build number 10 Copied 4 artifacts from "ovirt-engine-sdk_3.6_build-artifacts-fc23-x86_64" build number 12 Copied 14 artifacts from "otopi_3.6_create-rpms-el6-x86_64_merged" build number 4 Copied 19 artifacts from "otopi_3.6_create-rpms-el7-x86_64_merged" build number 4 ERROR: Unable to find project for artifact copy: otopi_3.6_create-rpms-fc22-x86_64_merged This may be due to incorrect project name or permission settings; see help for project name in job configuration.

1 9

[JIRA] (OVIRT-635) announce mailing list not working
by sbonazzo (oVirt JIRA) 14 Jul '16

14 Jul '16

sbonazzo created OVIRT-635: ------------------------------ Summary: announce mailing list not working Key: OVIRT-635 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-635 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra Hi, sent announce about 4.0.1 rc2 yesterday and it has not been published in http://lists.ovirt.org/pipermail/announce/2016-July/date.html can you please check? -- 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.148.3#100005)

1 0

RHEVM CI Jenkins daily report - 13
by jenkins＠jenkins.phx.ovirt.org 14 Jul '16

14 Jul '16

------=_Part_172_1840186734.1468450803709 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/13//artifact/exported-ar… Cheers, Jenkins ------=_Part_172_1840186734.1468450803709 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 - 13/07/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/deploy-to-ovirt_experimental_3.6/">deploy-to-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/lago_master_build-artifacts-fc24-x86_64/">lago_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> <tr><td> <a href="http://jenkins.ovirt.org/job/lago_master_check-merged-pipeline/">lago_master_check-merged-pipeline</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/lago_master_check-merged-trigger/">lago_master_check-merged-trigger</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-appliance_ovirt-4.0-pre_build-artifacts-…">ovirt-appliance_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-appliance_ovirt-4.0-snapshot_build-artif…">ovirt-appliance_ovirt-4.0-snapshot_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-appliance_ovirt-4.0_build-artifacts-el7-…">ovirt-appliance_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-dwh_3.6_build-artifacts-el6-x86_64/">ovirt-dwh_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-dwh_3.6_check-merged-el6-x86_64/">ovirt-dwh_3.6_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/ovirt-dwh_master_build-artifacts-fc24-x86_64/">ovirt-dwh_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> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-engine-sdk-java_4.0_create-rpms-fc24-x86…">ovirt-engine-sdk-java_4.0_create-rpms-fc24-x86_64_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/ovirt-engine-sdk-java_master_create-rpms-fc24-…">ovirt-engine-sdk-java_master_create-rpms-fc24-x86_64_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/ovirt-hosted-engine-ha_4.0_create-rpms-fc23-x8…">ovirt-hosted-engine-ha_4.0_create-rpms-fc23-x86_64_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/ovirt-hosted-engine-ha_master_create-rpms-el7-…">ovirt-hosted-engine-ha_master_create-rpms-el7-x86_64_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/ovirt-hosted-engine-ha_master_create-rpms-fc23…">ovirt-hosted-engine-ha_master_create-rpms-fc23-x86_64_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/ovirt-node-ng_master_build-artifacts-fc22-x86_…">ovirt-node-ng_master_build-artifacts-fc22-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-3.6_build-artifacts-fc22-x…">ovirt-node-ng_ovirt-3.6_build-artifacts-fc22-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-snapshot_build-artifac…">ovirt-node-ng_ovirt-4.0-snapshot_build-artifacts-fc22-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-fc22-x…">ovirt-node-ng_ovirt-4.0_build-artifacts-fc22-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-plugin-hosted-engine_ovirt-3.6_chec…">ovirt-node-plugin-hosted-engine_ovirt-3.6_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_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_publish-rpms_nightly/">ovirt_3.6_publish-rpms_nightly</a> </td><td> Collects RPMs from all oVirt projects (3.6 branches) and publish them to resources.ovirt.org yum repository.<br> 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/repos_4.0_check-closure_merged/">repos_4.0_check-closure_merged</a> </td><td> No Description </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_master_check-closure_merged/">repos_master_check-closure_merged</a> </td><td> No Description </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/test-repo_ovirt_experimental_master/">test-repo_ovirt_experimental_master</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/vdsm_master_check-merged-fc23-x86_64/">vdsm_master_check-merged-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> ------=_Part_172_1840186734.1468450803709--

1 0

[JIRA] (OVIRT-634) sending POST/PUT to gerrit to ... set a topic for example.
by Martin Mucha (oVirt JIRA) 13 Jul '16

13 Jul '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-634?page=com.atlassian.jira.p… ] Martin Mucha commented on OVIRT-634: ------------------------------------ Thanks for reply. I wasn't able to integrate gerrit cli into my workflow in past due to some errors with it, so I decided simply not to use it. But then I found REST api, which is documented and kinda works (as documented) for all GET requests. about adding reviewers — according to REST API, I don't have to do that manually. I can very easily create script, which will simply fire N requests (where N is number of patches) to add reviewers. Which is (far) more load-friendly than doing it via gerrit api. But I don't want to do only that. I can (easily) imagine more tasks (more complicated) I can automate for myself. All I need is rest api, which works for POSTs and PUTs. So the question is: does gerrit rest api work for such requests(and I just issuing wrong curl request), or it's disabled so noone can do that? I'm currently not interested in any other ways how to accomplish anything, I'm currently only interested in issuing rest requests. if such requests are allowed and you can see error in given curl command, I'd be grateful for help. > sending POST/PUT to gerrit to ... set a topic for example. > ---------------------------------------------------------- > > Key: OVIRT-634 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-634 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Martin Mucha > Assignee: infra > > Hi, > I'd like to ask, whether: > a) is even possible to pass requests to do some modifications on gerrit > b) if it is, then when I'd be glad if you can inform me, what I'm doing wrong in following command [1] > c) if it's not currently possible to pass such requests, I'd like to ask if they can be allowed. > Motivation: I have quite often longer topics, like 10 patches. Due to our work style they need to be rebased often and reverified. Or I need to specify same reviewers to all of them. etc. etc. This means I have to open *all* of them (takes ages to load) and do same actions over and over, which is time waste. Also, gerrit is (apparently) not designed to work under 'heavy' load, which means, that quite often page isn't loaded successfully. For example change is loaded, but allegedly I'm not logged in (which is not true), and because of that I have to hit refresh. This means, that I'm generating a lot of unnecessary load for gerrit server, while what I'd actually like to do is for example set topic to 10 patches, for which I do not need whole detail with all revisions to be loaded. > [1] > curl --digest -v -H Content-Type:application/json -u "mmucha:pass" -X PUT https://gerrit.ovirt.org/changes/58620/topic -d '{"topic":"test"}' > this return 403, and I'd like to know, if this is because of error in this command, or because this type of operations are generally not allowed. > Thanks, > M. -- This message was sent by Atlassian JIRA (v1000.148.2#100005)

1 0

[JIRA] (OVIRT-634) sending POST/PUT to gerrit to ... set a topic for example.
by Barak Korren (oVirt JIRA) 13 Jul '16

13 Jul '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-634?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-634: ------------------------------------ I can look this up in the gerrit cli/api. But I sometimes have a similar workflow and have successfully used git-review for most of this. With git-review you can put multipile patches in the same local brance and sumbit/update them all in a single command. The topic gets set according to the branch name (and you can do rebases locally with git). You still have to add reviewers manually, but we can setup groups to streamline that. בתאריך 13 ביולי 2016 17:31,‏ "Martin Mucha (oVirt JIRA)" < > sending POST/PUT to gerrit to ... set a topic for example. > ---------------------------------------------------------- > > Key: OVIRT-634 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-634 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Martin Mucha > Assignee: infra > > Hi, > I'd like to ask, whether: > a) is even possible to pass requests to do some modifications on gerrit > b) if it is, then when I'd be glad if you can inform me, what I'm doing wrong in following command [1] > c) if it's not currently possible to pass such requests, I'd like to ask if they can be allowed. > Motivation: I have quite often longer topics, like 10 patches. Due to our work style they need to be rebased often and reverified. Or I need to specify same reviewers to all of them. etc. etc. This means I have to open *all* of them (takes ages to load) and do same actions over and over, which is time waste. Also, gerrit is (apparently) not designed to work under 'heavy' load, which means, that quite often page isn't loaded successfully. For example change is loaded, but allegedly I'm not logged in (which is not true), and because of that I have to hit refresh. This means, that I'm generating a lot of unnecessary load for gerrit server, while what I'd actually like to do is for example set topic to 10 patches, for which I do not need whole detail with all revisions to be loaded. > [1] > curl --digest -v -H Content-Type:application/json -u "mmucha:pass" -X PUT https://gerrit.ovirt.org/changes/58620/topic -d '{"topic":"test"}' > this return 403, and I'd like to know, if this is because of error in this command, or because this type of operations are generally not allowed. > Thanks, > M. -- This message was sent by Atlassian JIRA (v1000.148.2#100005)

1 0

[JIRA] (OVIRT-634) sending POST/PUT to gerrit to ... set a topic for example.
by Martin Mucha (oVirt JIRA) 13 Jul '16

13 Jul '16

Martin Mucha created OVIRT-634: ---------------------------------- Summary: sending POST/PUT to gerrit to ... set a topic for example. Key: OVIRT-634 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-634 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Martin Mucha Assignee: infra Hi, I'd like to ask, whether: a) is even possible to pass requests to do some modifications on gerrit b) if it is, then when I'd be glad if you can inform me, what I'm doing wrong in following command [1] c) if it's not currently possible to pass such requests, I'd like to ask if they can be allowed. Motivation: I have quite often longer topics, like 10 patches. Due to our work style they need to be rebased often and reverified. Or I need to specify same reviewers to all of them. etc. etc. This means I have to open *all* of them (takes ages to load) and do same actions over and over, which is time waste. Also, gerrit is (apparently) not designed to work under 'heavy' load, which means, that quite often page isn't loaded successfully. For example change is loaded, but allegedly I'm not logged in (which is not true), and because of that I have to hit refresh. This means, that I'm generating a lot of unnecessary load for gerrit server, while what I'd actually like to do is for example set topic to 10 patches, for which I do not need whole detail with all revisions to be loaded. [1] curl --digest -v -H Content-Type:application/json -u "mmucha:pass" -X PUT https://gerrit.ovirt.org/changes/58620/topic -d '{"topic":"test"}' this return 403, and I'd like to know, if this is because of error in this command, or because this type of operations are generally not allowed. Thanks, M. -- This message was sent by Atlassian JIRA (v1000.148.2#100005)

2 1

[JIRA] (OVIRT-632) upgrade Foreman to 1.8 or newer
by Evgheni Dereveanchin (oVirt JIRA) 13 Jul '16

13 Jul '16

Evgheni Dereveanchin created OVIRT-632: ------------------------------------------ Summary: upgrade Foreman to 1.8 or newer Key: OVIRT-632 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-632 Project: oVirt - virtualization made easy Issue Type: Task Components: Foreman Reporter: Evgheni Dereveanchin Assignee: infra The currently installed version of Foreman is buggy, for example it misreads the primary interface on VMs which causes DHCP issues as the wrong MAC is uesd. Foreman 1.8 fixes this by adding a "Ignore interfaces with matching identifier" filter in provisioning settings. -- This message was sent by Atlassian JIRA (v1000.148.2#100005)

1 0

RHEVM CI Jenkins daily report - 12
by jenkins＠jenkins.phx.ovirt.org 13 Jul '16

13 Jul '16

------=_Part_151_1419667088.1468364404005 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/12//artifact/exported-ar… Cheers, Jenkins ------=_Part_151_1419667088.1468364404005 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/07/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/deploy-to-ovirt_experimental_3.6/">deploy-to-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/lago_master_build-artifacts-fc24-x86_64/">lago_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> <tr><td> <a href="http://jenkins.ovirt.org/job/lago_master_check-merged-pipeline/">lago_master_check-merged-pipeline</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/lago_master_check-merged-trigger/">lago_master_check-merged-trigger</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-dwh_3.6_build-artifacts-el6-x86_64/">ovirt-dwh_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-dwh_3.6_build-artifacts-fc23-x86_64/">ovirt-dwh_3.6_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/ovirt-dwh_3.6_check-merged-el6-x86_64/">ovirt-dwh_3.6_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/ovirt-dwh_3.6_check-merged-fc23-x86_64/">ovirt-dwh_3.6_check-merged-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/ovirt-dwh_master_build-artifacts-fc24-x86_64/">ovirt-dwh_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> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-engine-sdk-java_4.0_create-rpms-fc24-x86…">ovirt-engine-sdk-java_4.0_create-rpms-fc24-x86_64_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/ovirt-engine-sdk-java_master_create-rpms-fc24-…">ovirt-engine-sdk-java_master_create-rpms-fc24-x86_64_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/ovirt-engine-sdk-ruby_master_build-artifacts-f…">ovirt-engine-sdk-ruby_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> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-hosted-engine-setup_master_check-merged-…">ovirt-hosted-engine-setup_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-node-ng_master_build-artifacts-fc22-x86_…">ovirt-node-ng_master_build-artifacts-fc22-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-3.6_build-artifacts-fc22-x…">ovirt-node-ng_ovirt-3.6_build-artifacts-fc22-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-fc22-x…">ovirt-node-ng_ovirt-4.0_build-artifacts-fc22-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-plugin-hosted-engine_ovirt-3.6_chec…">ovirt-node-plugin-hosted-engine_ovirt-3.6_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_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_publish-rpms_nightly/">ovirt_3.6_publish-rpms_nightly</a> </td><td> Collects RPMs from all oVirt projects (3.6 branches) and publish them to resources.ovirt.org yum repository.<br> 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_merged/">repos_master_check-closure_merged</a> </td><td> No Description </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_check-merged-fc23-x86_64/">vdsm_master_check-merged-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> ------=_Part_151_1419667088.1468364404005--

4 5

[JIRA] (OVIRT-631) intermittent DNS issues in phx.ovirt.org zone
by Evgheni Dereveanchin (oVirt JIRA) 13 Jul '16

13 Jul '16

Evgheni Dereveanchin created OVIRT-631: ------------------------------------------ Summary: intermittent DNS issues in phx.ovirt.org zone Key: OVIRT-631 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-631 Project: oVirt - virtualization made easy Issue Type: Bug Components: Foreman Reporter: Evgheni Dereveanchin Assignee: infra Priority: High There are jobs failing due to name resolution issues: Could not resolve proxy: proxy.phx.ovirt.org; Unknown error -- This message was sent by Atlassian JIRA (v1000.148.2#100005)

1 0

[JIRA] (OVIRT-631) intermittent DNS issues in phx.ovirt.org zone
by Evgheni Dereveanchin (oVirt JIRA) 13 Jul '16

13 Jul '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-631?page=com.atlassian.jira.p… ] Evgheni Dereveanchin reassigned OVIRT-631: ------------------------------------------ Assignee: Evgheni Dereveanchin (was: infra) > intermittent DNS issues in phx.ovirt.org zone > --------------------------------------------- > > Key: OVIRT-631 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-631 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Foreman > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > Priority: High > > There are jobs failing due to name resolution issues: > Could not resolve proxy: proxy.phx.ovirt.org; Unknown error -- This message was sent by Atlassian JIRA (v1000.148.2#100005)

1 0