August 2016 - Infra - oVirt List Archives

[JIRA] (OVIRT-681) [URGENT] boolean parameters not passed anymore to jenkins jobs
by snaftaly (oVirt JIRA) 14 Aug '16

14 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-681?page=com.atlassian.jira.p… ] snaftaly commented on OVIRT-681: -------------------------------- [~eedri], [~sbonazzo(a)redhat.com] I started working on moving the jobs to yaml (without matrix jobs). I hope my patch will be ready today. > [URGENT] boolean parameters not passed anymore to jenkins jobs > -------------------------------------------------------------- > > Key: OVIRT-681 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-681 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > Attachments: image.png > > > Hi, > looks like repository closure jobs are not working anymore because the > boolean parameters are not passed anymore to the job environment. > Can you please check why this happens? > See for example > http://jenkins.ovirt.org/user/sbonazzo/my-views/view/Repo%20status/job/repo… > -- > 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.245.0#100009)

1 0

[JIRA] (OVIRT-681) [URGENT] boolean parameters not passed anymore to jenkins jobs
by eyal edri [Administrator] (oVirt JIRA) 14 Aug '16

14 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-681?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-681: ------------------------------------------------- Can we get rid of the matrix plugin and move to use normal jobs, should be easy with YAML and don't need the complexity of matrix jobs... On Sun, Aug 14, 2016 at 10:39 AM, Gil Shinar (oVirt JIRA) < -- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) > [URGENT] boolean parameters not passed anymore to jenkins jobs > -------------------------------------------------------------- > > Key: OVIRT-681 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-681 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > Attachments: image.png > > > Hi, > looks like repository closure jobs are not working anymore because the > boolean parameters are not passed anymore to the job environment. > Can you please check why this happens? > See for example > http://jenkins.ovirt.org/user/sbonazzo/my-views/view/Repo%20status/job/repo… > -- > 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.245.0#100009)

1 0

[JIRA] (OVIRT-681) [URGENT] boolean parameters not passed anymore to jenkins jobs
by Gil Shinar (oVirt JIRA) 14 Aug '16

14 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-681?page=com.atlassian.jira.p… ] Gil Shinar updated OVIRT-681: ----------------------------- Attachment: image.png Hi Sandro, I haven't had the chance to use Matrix jobs so it was a challenge for me investigate :-) I have found the following bug: https://issues.jenkins-ci.org/browse/JENKINS-34758 Due to a security update, parameters stopped being passed to child jobs. According to changelog, matrix job plugin version 1.7 should fix that: [image: Inline image 1] I'll upgrade the plugin but restart might be needed so you'll tell us when. Gil On Sat, Aug 13, 2016 at 8:49 AM, sbonazzo (oVirt JIRA) < > [URGENT] boolean parameters not passed anymore to jenkins jobs > -------------------------------------------------------------- > > Key: OVIRT-681 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-681 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > Attachments: image.png > > > Hi, > looks like repository closure jobs are not working anymore because the > boolean parameters are not passed anymore to the job environment. > Can you please check why this happens? > See for example > http://jenkins.ovirt.org/user/sbonazzo/my-views/view/Repo%20status/job/repo… > -- > 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.245.0#100009)

2 1

[JIRA] (OVIRT-681) [URGENT] boolean parameters not passed anymore to jenkins jobs
by sbonazzo (oVirt JIRA) 14 Aug '16

14 Aug '16

sbonazzo created OVIRT-681: ------------------------------ Summary: [URGENT] boolean parameters not passed anymore to jenkins jobs Key: OVIRT-681 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-681 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra Hi, looks like repository closure jobs are not working anymore because the boolean parameters are not passed anymore to the job environment. Can you please check why this happens? See for example http://jenkins.ovirt.org/user/sbonazzo/my-views/view/Repo%20status/job/repo… -- 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.245.0#100009)

2 1

[JIRA] (OVIRT-683) [gerrit hooks] bug status shouldn't move to MODIFIED if on master branch
by eyal edri [Administrator] (oVirt JIRA) 14 Aug '16

14 Aug '16

eyal edri [Administrator] created OVIRT-683: ----------------------------------------------- Summary: [gerrit hooks] bug status shouldn't move to MODIFIED if on master branch Key: OVIRT-683 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-683 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: eyal edri [Administrator] Assignee: infra consider master branch also in the logic for moving to MODIFIED state, suggested patch: https://gerrit.ovirt.org/#/c/61073/ -- This message was sent by Atlassian JIRA (v1000.245.0#100009)

1 0

[JIRA] (OVIRT-683) [gerrit hooks] bug status shouldn't move to MODIFIED if on master branch
by eyal edri [Administrator] (oVirt JIRA) 14 Aug '16

14 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-683?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-683: -------------------------------------------- Epic Link: OVIRT-411 > [gerrit hooks] bug status shouldn't move to MODIFIED if on master branch > ------------------------------------------------------------------------ > > Key: OVIRT-683 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-683 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > > consider master branch also in the logic for moving to MODIFIED state, > suggested patch: https://gerrit.ovirt.org/#/c/61073/ -- This message was sent by Atlassian JIRA (v1000.245.0#100009)

1 0

oVirt Bot and oVirt Meetings
by Sandro Bonazzola 14 Aug '16

14 Aug '16

Hi, is the oVirt Bot meant to be down? The oVIrt website still mention it: http://www.ovirt.org/community/about/meetings/ http://www.ovirt.org/develop/infra/ovirtbot/ http://www.ovirt.org/develop/infra/running-ovirtbot/ http://www.ovirt.org/develop/infra/infrastructure-team-meetings/ Are listed meetings still valid? I don't think so. http://www.ovirt.org/community/about/meetings/ -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 1

[JIRA] (OVIRT-682) Improve CI logging - check if its possible to include mock errors in console output
by eyal edri [Administrator] (oVirt JIRA) 14 Aug '16

14 Aug '16

eyal edri [Administrator] created OVIRT-682: ----------------------------------------------- Summary: Improve CI logging - check if its possible to include mock errors in console output Key: OVIRT-682 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-682 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: eyal edri [Administrator] Assignee: infra On Fri, Aug 12, 2016 at 8:08 PM, Nir Soffer <nsoffer(a)redhat.com> wrote: > Hi all, > > Lately vdsm builds are failing in the install packages stage with > this unhelpful error: > > 13:59:42 INFO: installing package(s): autoconf automake gdb ... > 13:59:53 ERROR: Command failed. See logs for output. > > I downloaded the logs.tgz file from > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24- > x86_64/1154/artifact/exported-artifacts/logs.tgz > > And indeed in /./vdsm/logs/mocker-fedora-24-x86_64.fc24.install_packages/ > root.log > I found found this error: > > DEBUG util.py:421: Error: Package: > python-ioprocess-0.17.0-1.201608111609.gitbd272f2.fc24.noarch > (ovirt-snapshot) > DEBUG util.py:421: Requires: ioprocess = > 0.17.0-1.201608111609.gitbd272f2.fc24 > DEBUG util.py:421: Available: > ioprocess-0.15.1-1.fc24.x86_64 (fedora) > DEBUG util.py:421: ioprocess = 0.15.1-1.fc24 > DEBUG util.py:421: Available: > ioprocess-0.16.1-1.fc24.x86_64 (updates) > DEBUG util.py:421: ioprocess = 0.16.1-1.fc24 > DEBUG util.py:421: Available: > ioprocess-0.17.0-1.201607121058.gitbd272f2.fc24.x86_64 > (ovirt-snapshot) > DEBUG util.py:421: ioprocess = > 0.17.0-1.201607121058.gitbd272f2.fc24 > DEBUG util.py:421: Available: > ioprocess-0.17.0-1.201608111129.gitbd272f2.fc24.x86_64 > (ovirt-snapshot) > DEBUG util.py:421: ioprocess = > 0.17.0-1.201608111129.gitbd272f2.fc24 > > So we have 2 issues here: > > 1. We need *all* errors in the console > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24- > x86_64/1154/console Not sure its possible or easy to do, these errors usually come from mock and are not relevant to the code running on the console. I've cc'd infra-support and updated topic to track it and check our options. Going foward, we might want to install a log collector like logstash and then searching errors there should be much easier. > > > 2. Someone need to fix the ovirt-snapshot repository - it should have > the missing ioprocess > package. > Maybe the project xml is not correct? > > Nir > -- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.245.0#100009)

1 0

Improve CI logging - check if its possible to include mock errors in console output
by Eyal Edri 14 Aug '16

14 Aug '16

On Fri, Aug 12, 2016 at 8:08 PM, Nir Soffer <nsoffer(a)redhat.com> wrote: > Hi all, > > Lately vdsm builds are failing in the install packages stage with > this unhelpful error: > > 13:59:42 INFO: installing package(s): autoconf automake gdb ... > 13:59:53 ERROR: Command failed. See logs for output. > > I downloaded the logs.tgz file from > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24- > x86_64/1154/artifact/exported-artifacts/logs.tgz > > And indeed in /./vdsm/logs/mocker-fedora-24-x86_64.fc24.install_packages/ > root.log > I found found this error: > > DEBUG util.py:421: Error: Package: > python-ioprocess-0.17.0-1.201608111609.gitbd272f2.fc24.noarch > (ovirt-snapshot) > DEBUG util.py:421: Requires: ioprocess = > 0.17.0-1.201608111609.gitbd272f2.fc24 > DEBUG util.py:421: Available: > ioprocess-0.15.1-1.fc24.x86_64 (fedora) > DEBUG util.py:421: ioprocess = 0.15.1-1.fc24 > DEBUG util.py:421: Available: > ioprocess-0.16.1-1.fc24.x86_64 (updates) > DEBUG util.py:421: ioprocess = 0.16.1-1.fc24 > DEBUG util.py:421: Available: > ioprocess-0.17.0-1.201607121058.gitbd272f2.fc24.x86_64 > (ovirt-snapshot) > DEBUG util.py:421: ioprocess = > 0.17.0-1.201607121058.gitbd272f2.fc24 > DEBUG util.py:421: Available: > ioprocess-0.17.0-1.201608111129.gitbd272f2.fc24.x86_64 > (ovirt-snapshot) > DEBUG util.py:421: ioprocess = > 0.17.0-1.201608111129.gitbd272f2.fc24 > > So we have 2 issues here: > > 1. We need *all* errors in the console > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24- > x86_64/1154/console Not sure its possible or easy to do, these errors usually come from mock and are not relevant to the code running on the console. I've cc'd infra-support and updated topic to track it and check our options. Going foward, we might want to install a log collector like logstash and then searching errors there should be much easier. > > > 2. Someone need to fix the ovirt-snapshot repository - it should have > the missing ioprocess > package. > Maybe the project xml is not correct? > > Nir > -- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

1 0

oVirt infra daily report - unstable production jobs - 45
by jenkins＠jenkins.phx.ovirt.org 13 Aug '16

13 Aug '16

------=_Part_130_1001960909.1471129204561 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/45//artifact/exported-ar… Cheers, Jenkins ------=_Part_130_1001960909.1471129204561 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/08/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/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-engine_4.0_upgrade-from-3.6_el7_merged/">ovirt-engine_4.0_upgrade-from-3.6_el7_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-engine_4.0_upgrade-from-4.0_el7_merged/">ovirt-engine_4.0_upgrade-from-4.0_el7_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_me…">ovirt-engine_master_upgrade-from-master_el7_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/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-3.6_build-artifacts-el7-x8…">ovirt-node-ng_ovirt-3.6_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-snapshot_build-artifac…">ovirt-node-ng_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-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_4.0_he-system-tests/">ovirt_4.0_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_4.0_system-tests/">ovirt_4.0_system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_system-tests/">ovirt_master_system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.0/">test-repo_ovirt_experimental_4.0</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/">test-repo_ovirt_experimental_master</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/vdsm_4.0_check-merged-fc23-x86_64/">vdsm_4.0_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/vdsm_master_build-artifacts-el7-ppc64le/">vdsm_master_build-artifacts-el7-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-el7-x86_64/">vdsm_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> ------=_Part_130_1001960909.1471129204561--

1 0