- Infra - oVirt List Archives

Change 21 [6] failed system tests
by oVirt Jenkins 21 Mar '17

21 Mar '17

Change 21 [6] is probably the reason behind recent system test failures in the "numbers" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/21/

1 0

Change 20 [4] failed system tests
by oVirt Jenkins 21 Mar '17

21 Mar '17

Change 20 [4] is probably the reason behind recent system test failures in the "numbers" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/20/

1 0

Change 19 [1] passed system tests
by oVirt Jenkins 21 Mar '17

21 Mar '17

Change 19 [1] successfully passed the system tests invoked from the "numbers" queue. For further details about the change see: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/19/

1 0

Change 18 [4] passed system tests
by oVirt Jenkins 21 Mar '17

21 Mar '17

Change 18 [4] successfully passed the system tests invoked from the "numbers" queue. For further details about the change see: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/18/

1 0

Change 17 [13] passed system tests
by oVirt Jenkins 21 Mar '17

21 Mar '17

Change 17 [13] successfully passed the system tests invoked from the "numbers" queue. For further details about the change see: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/17/

1 0

Change 21 [6] queued for testing
by oVirt Jenkins 21 Mar '17

21 Mar '17

Change 21 [6] was successfully added into the "numbers" queue for testing. Further messages will be sent when test results are available. For further details about the change see: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/21/

1 0

Change 20 [4] queued for testing
by oVirt Jenkins 21 Mar '17

21 Mar '17

Change 20 [4] was successfully added into the "numbers" queue for testing. Further messages will be sent when test results are available. For further details about the change see: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/20/

1 0

Change 19 [1] queued for testing
by oVirt Jenkins 21 Mar '17

21 Mar '17

Change 19 [1] was successfully added into the "numbers" queue for testing. Further messages will be sent when test results are available. For further details about the change see: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/19/

1 0

Change 18 [4] queued for testing
by oVirt Jenkins 21 Mar '17

21 Mar '17

Change 18 [4] was successfully added into the "numbers" queue for testing. Further messages will be sent when test results are available. For further details about the change see: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/18/

1 0

Change 17 [13] queued for testing
by oVirt Jenkins 21 Mar '17

21 Mar '17

Change 17 [13] was successfully added into the "numbers" queue for testing. Further messages will be sent when test results are available. For further details about the change see: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/17/

1 0

Change 14 [1] passed system tests
by oVirt Jenkins 21 Mar '17

21 Mar '17

Change 14 [1] successfully passed the system tests invoked from the "numbers" queue. For further details about the change see: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/14/

1 0

Change 13 [4] passed system tests
by oVirt Jenkins 21 Mar '17

21 Mar '17

Change 13 [4] successfully passed the system tests invoked from the "numbers" queue. For further details about the change see: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/13/

1 0

Change 15 [4] passed system tests
by oVirt Jenkins 21 Mar '17

21 Mar '17

Change 15 [4] successfully passed the system tests invoked from the "numbers" queue. For further details about the change see: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/15/

1 0

Change 16 [6] passed system tests
by oVirt Jenkins 21 Mar '17

21 Mar '17

Change 16 [6] successfully passed the system tests invoked from the "numbers" queue. For further details about the change see: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/16/

1 0

Change 12 [2] passed system tests
by oVirt Jenkins 21 Mar '17

21 Mar '17

Change 12 [2] successfully passed the system tests invoked from the "numbers" queue. For further details about the change see: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/12/

1 0

Change 16 [6] queued for testing
by oVirt Jenkins 21 Mar '17

21 Mar '17

Change 16 [6] was successfully added into the "numbers" queue for testing. Further messages will be sent when test results are available. For further details about the change see: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/16/

1 0

Change 15 [4] queued for testing
by oVirt Jenkins 21 Mar '17

21 Mar '17

Change 15 [4] was successfully added into the "numbers" queue for testing. Further messages will be sent when test results are available. For further details about the change see: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/15/

1 0

Change 14 [1] queued for testing
by oVirt Jenkins 21 Mar '17

21 Mar '17

Change 14 [1] was successfully added into the "numbers" queue for testing. Further messages will be sent when test results are available. For further details about the change see: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/14/

1 0

Change 13 [4] queued for testing
by oVirt Jenkins 21 Mar '17

21 Mar '17

Change 13 [4] was successfully added into the "numbers" queue for testing. Further messages will be sent when test results are available. For further details about the change see: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/13/

1 0

Change 12 [2] queued for testing
by oVirt Jenkins 21 Mar '17

21 Mar '17

Change 12 [2] was successfully added into the "numbers" queue for testing. Further messages will be sent when test results are available. For further details about the change see: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/12/

1 0

Get Involved with the oVirt Project! Spring 2017 Edition
by Sandro Bonazzola 21 Mar '17

21 Mar '17

Hi, Got some time to spare? Join us on the oVirt project! oVirt is a feature rich server virtualization management system with advanced capabilities. It also provides a crucial venue for user and developer cooperation, and is the first truly open and comprehensive data center virtualization management initiative. If you are new to oVirt, we recommend that you visit the develop <https://www.ovirt.org/develop/> page to learn more about the project, and the working with Gerrit <https://www.ovirt.org/develop/dev-process/working-with-gerrit/> page for more about our code review system. If you haven’t worked with Gerrit before, we recommend you visit the introduction to Gerrit <https://gerrit-review.googlesource.com/Documentation> page. On our community page <https://www.ovirt.org/community/> you’ll discover the many ways in which you can contribute to the project, even without programming skills. More suggestions? Below you’ll find other ways in which you can contribute to the oVirt project. Keep ‘em Fresh Like the idea of having fresh disk images of your favorite distribution in the oVirt Glance repository? You can help in two ways: First, test existing online images to ensure that they work with cloud-init. Second, create an online image and report your success to devel(a)ovirt.org. We’ll be happy to upload the images once they are ready. Get Vdsm Running on Debian If you like Debian and have programming or packaging skills, you can help with the ongoing effort to get VDSM running on Debian <https://www.ovirt.org/develop/release-management/features/debian-support-fo…>. All the current work on Debian (VDSM and related packages) can be found in the Debian git repositories <http://git.debian.org/>. You can also keep up to date on how the work is progressing by subscribing to the oVirt devel mailing list <http://lists.ovirt.org/mailman/listinfo/devel>. Fix Some Bugs These bugs are just waiting to be resolved: Bug ID Summary 1411133 Hosted-Engine: iscsi activation storage failing 1209881 [RFE] Remove iptables from hosted-engine.spec file to be able to deploy hosted-engine without firewall services installed 1353713 [RFE] - iSCSI Setup Should use different User/Password For Discovery and Portal 1130445 [TEXT] - If engine-setup asks for updates and choice is no, suggest '--offline' on re-run. 1174236 [RFE] Integrate installation with Server Roles of Fedora Server 1356425 [TEXT] 'hosted-engine --vm-start' said it destroyed the VM 1328488 The engine fails with oracle java8 Port oVirt to Your Favorite Distribution Are you sure-handed at packaging software, and using a distribution currently unsupported by oVirt? Help to get oVirt ported to any of the following distributions: Fedora <http://lists.ovirt.org/pipermail/devel/2015-September/011426.html> CentOS <https://wiki.centos.org/SpecialInterestGroup/Virtualization> Gentoo <https://wiki.gentoo.org/wiki/OVirt>. Also, check out Google Summer of Code <https://wiki.gentoo.org/wiki/Google_Summer_of_Code/2016/Ideas> to learn how you can contribute to Gentoo and get paid for it! Debian <http://www.ovirt.org/develop/release-management/features/debian-support-for…>: Archlinux <http://www.ovirt.org/develop/developer-guide/arch-linux/> OpenSUSE <https://build.opensuse.org/project/show/Virtualization:oVirt> Get into DevOps If you love DevOps and find yourself counting stable builds in Jenkins CI while trying to fall asleep, then the oVirt infrastructure team is looking for you! Join us and dive into the latest and coolest DevOps tools today! Check out these open tasks <https://ovirt-jira.atlassian.net/secure/RapidBoard.jspa?rapidView=6.>. You can also help by telling us how you use oVirt in your DevOps environment. Email us at devel(a)ovirt.org (Please use [DevOps] in the subject line. For more information on oVirt DevOps, visit oVirt infrastructure docs <http://ovirt-infra-docs.readthedocs.io/en/latest/> and oVirt infra documentation <http://www.ovirt.org/develop/infra/infrastructure-documentation/>. Improve the oVirt System Testing Make oVirt system testing <https://gerrit.ovirt.org/gitweb?p=ovirt-system-tests.git;a=summary> - and the Lago system <https://github.com/lago-project/lago> that runs it - even better. Visit Lago project documentation <http://lago.readthedocs.io/en/stable/> to learn how to run the test suite yourself. More Bugs, No Coding Required No time for DevOps and you are not a programer? You can still contribute. Here are some easy bugs to fix <https://bugzilla.redhat.com/buglist.cgi?quicksearch=classification%3Aovirt%…> that don’t require a single line of code. Tests to Run Do you prefer to test things? Here are some test cases you can try <http://www.ovirt.org/develop/infra/testing/>, using nightly snapshots <http://www.ovirt.org/develop/dev-process/install-nightly-snapshot/>. Switching to Fedora 25 For oVirt 4.2, support for Fedora will be based on Fedora 25. You can help to get it ready by running nightly snapshots <http://www.ovirt.org/develop/dev-process/install-nightly-snapshot/> and reporting any issues. Create Your Own Test Cases We’d love you to contribute some much needed test cases for oVirt features <http://www.ovirt.org/develop/release-management/features/>. Get Creative You are welcome to contribute artwork, such as oVirt live backgrounds and covers, release banners, stickers, and t-shirt designs. Check out Fedora artworks <https://fedoraproject.org/wiki/Artwork#Resources> for inspiration. Get Alternative Into alternative architectures? Test ppc64le <https://cbs.centos.org/repos/virt7-ovirt-41-release/ppc64le/> and aarch64 <https://cbs.centos.org/repos/virt7-ovirt-41-release/aarch64/> packages from CentOS Virt SIG. Talk to Us! Feel free to ask any other question about development by emailing us at devel(a)ovirt.org, or by reaching out on the IRC channel <https://www.ovirt.org/community/>. Spread the Good News Help to spread the word about oVirt! We are the complete virtual machine management system that’s free and comes with an impressive list of enterprise capabilities <http://www.zdnet.com/article/how-much-longer-can-red-hats-ovirt-remain-cove…> including live migration, high availability, load balancing, a self-hosted engine, an intuitive user-interface, and much more. How to Contribute If you’d like to get involved, we’d love to hear from you! Simply shoot us an email at devel(a)ovirt.org and tell us how you’d like to contribute. We look forward to hearing from you!. The oVirt Development Team oVirt: Better technology. Faster Innovation. Powered by community innovation.

1 0

oVirt infra daily report - unstable production jobs - 264
by jenkins＠jenkins.phx.ovirt.org 20 Mar '17

20 Mar '17

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

1 0

Change 11 [4] passed system tests
by oVirt Jenkins 20 Mar '17

20 Mar '17

Change 11 [4] successfully passed the system tests invoked from the "numbers" queue. For further details about the change see: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/11/

1 0

Change 10 [3] failed system tests
by oVirt Jenkins 20 Mar '17

20 Mar '17

Change 10 [3] is probably the reason behind recent system test failures in the "numbers" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/10/

1 0

Change 9 [7] passed system tests
by oVirt Jenkins 20 Mar '17

20 Mar '17

Change 9 [7] successfully passed the system tests invoked from the "numbers" queue. For further details about the change see: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/9/

1 0

Change 11 [4] queued for testing
by oVirt Jenkins 20 Mar '17

20 Mar '17

Change 11 [4] was successfully added into the "numbers" queue for testing. Further messages will be sent when test results are available. For further details about the change see: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/11/

1 0

Change 10 [3] queued for testing
by oVirt Jenkins 20 Mar '17

20 Mar '17

Change 10 [3] was successfully added into the "numbers" queue for testing. Further messages will be sent when test results are available. For further details about the change see: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/10/

1 0

Change 9 [7] queued for testing
by oVirt Jenkins 20 Mar '17

20 Mar '17

Change 9 [7] was successfully added into the "numbers" queue for testing. Further messages will be sent when test results are available. For further details about the change see: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/9/

1 0

[JIRA] (OVIRT-1265) Please update the pipeline stage view plugin
by Barak Korren (oVirt JIRA) 20 Mar '17

20 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1265?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1265: ----------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Please update the pipeline stage view plugin > -------------------------------------------- > > Key: OVIRT-1265 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1265 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: Evgheni Dereveanchin > Priority: High > > We are using a very old version. It is incompatible with the non-deprecated 'stage' syntax that includes a code block. > I've tried the update on the staging server, It also requires updates to the following plugins: > - bouncycastle API Plugin > - Pipeline: API > - Pipeline: REST API Plugin -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

[JIRA] (OVIRT-1265) Please update the pipeline stage view plugin
by Barak Korren (oVirt JIRA) 20 Mar '17

20 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1265?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1265: ------------------------------------- I guess Puppet downgraded it back by now, but I was able to confirm this update is indeed what we need for the stages to be displayed properly > Please update the pipeline stage view plugin > -------------------------------------------- > > Key: OVIRT-1265 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1265 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Priority: High > > We are using a very old version. It is incompatible with the non-deprecated 'stage' syntax that includes a code block. > I've tried the update on the staging server, It also requires updates to the following plugins: > - bouncycastle API Plugin > - Pipeline: API > - Pipeline: REST API Plugin -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

[JIRA] (OVIRT-1265) Please update the pipeline stage view plugin
by Barak Korren (oVirt JIRA) 20 Mar '17

20 Mar '17

Barak Korren created OVIRT-1265: ----------------------------------- Summary: Please update the pipeline stage view plugin Key: OVIRT-1265 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1265 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Reporter: Barak Korren Assignee: infra Priority: High We are using a very old version. It is incompatible with the non-deprecated 'stage' syntax that includes a code block. I've tried the update on the staging server, It also requires updates to the following plugins: - bouncycastle API Plugin - Pipeline: API - Pipeline: REST API Plugin -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

[JIRA] (OVIRT-1265) Please update the pipeline stage view plugin
by Barak Korren (oVirt JIRA) 20 Mar '17

20 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1265?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1265: -------------------------------- Epic Link: OVIRT-400 > Please update the pipeline stage view plugin > -------------------------------------------- > > Key: OVIRT-1265 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1265 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Priority: High > > We are using a very old version. It is incompatible with the non-deprecated 'stage' syntax that includes a code block. > I've tried the update on the staging server, It also requires updates to the following plugins: > - bouncycastle API Plugin > - Pipeline: API > - Pipeline: REST API Plugin -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

Change 8 [8] failed system tests
by oVirt Jenkins 20 Mar '17

20 Mar '17

Change 8 [8] is probably the reason behind recent system test failures in the "numbers" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/8/

1 0

Change 8 [8] queued for testing
by oVirt Jenkins 20 Mar '17

20 Mar '17

Change 8 [8] was successfully added into the "numbers" queue for testing. Further messages will be sent when test results are available. For further details about the change see: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/8/

1 0

Change 7 [11] passed system tests
by oVirt Jenkins 20 Mar '17

20 Mar '17

Change 7 [11] successfully passed the system tests invoked from the "numbers" queue. For further details about the change see: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/7/

1 0

Change 7 [11] queued for testing
by oVirt Jenkins 20 Mar '17

20 Mar '17

Change 7 [11] was successfully added into the "numbers" queue for testing. Further messages will be sent when test results are available. For further details about the change see: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/7/

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #1007 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 20 Mar '17

20 Mar '17

------=_Part_179_2038595660.1490018348881 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/1007/, Build Number: 1007, Build Status: FAILURE ------=_Part_179_2038595660.1490018348881--

1 2

[oVirt Jenkins] ovirt_4.1_he-system-tests - Build # 50 - Failure!
by jenkins＠jenkins.phx.ovirt.org 20 Mar '17

20 Mar '17

------=_Part_185_1497406029.1490019993755 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt_4.1_he-system-tests/ Build: http://jenkins.ovirt.org/job/ovirt_4.1_he-system-tests/50/ Build Number: 50 Build Status: Failure Triggered By: Started by user Simone Tiraboschi ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #50 No changes ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_185_1497406029.1490019993755--

1 2

[JIRA] (OVIRT-926) check why 3.6 experimental job failed even if not error in shown on job
by Gil Shinar (oVirt JIRA) 20 Mar '17

20 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-926?page=com.atlassian.jira.p… ] Gil Shinar commented on OVIRT-926: ---------------------------------- I haven't seen it since but maybe all infra owners should reply. > check why 3.6 experimental job failed even if not error in shown on job > ----------------------------------------------------------------------- > > Key: OVIRT-926 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-926 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > Labels: ost_failures > > http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/4322/ > [~gbenhaim@redhat.com][~ngoldin@redhat.com][~ederevea][~bkorren@redhat.com] any ideas? -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

[JIRA] (OVIRT-1170) add option to disable networking (or have it off by default)
by Greg Sheremeta (oVirt JIRA) 20 Mar '17

20 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1170?page=com.atlassian.jira.… ] Greg Sheremeta commented on OVIRT-1170: --------------------------------------- Yes, still need this. I just haven't gotten back to it yet. I'll test soon. > add option to disable networking (or have it off by default) > ------------------------------------------------------------ > > Key: OVIRT-1170 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1170 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Greg Sheremeta > Assignee: infra > > Add option to disable networking (or have it off by default). Basically, we want to prevent a job from accessing the internet if we want repeatable builds and/or are doing a downstream build somewhere else. Other/downstream build environments often have networking off. Copr has an option: (See: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.… ) > In particular, the ovirt-engine-nodejs-modules build-artifacts job *tries* to stay offline, but an evil node module called 'phantomjs' connects to the internet in a post-offline-install hook. I'd like the option to disallow that and have the build fail. -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

[JIRA] (OVIRT-1084) build a generic yaml template for both github and gerrit projects
by eyal edri [Administrator] (oVirt JIRA) 20 Mar '17

20 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1084?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1084: --------------------------------------------- Summary: build a generic yaml template for both github and gerrit projects (was: Merge github and gerrit jobs) > build a generic yaml template for both github and gerrit projects > ----------------------------------------------------------------- > > Key: OVIRT-1084 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1084 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Pavel Zhukov > Assignee: infra > Priority: Low > > As per https://ovirt-jira.atlassian.net/browse/OVIRT-970 gerrit and github jobs contan a lot of common code and features so they should be merged and _github_ suffix removed from the job names. -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

[JIRA] (OVIRT-1084) Merge github and gerrit jobs
by eyal edri [Administrator] (oVirt JIRA) 20 Mar '17

20 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1084?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1084: -------------------------------------------------- OK, didn't understand it from the name of the ticket, i'll rename the ticket to reflect what needs to be done. > Merge github and gerrit jobs > ---------------------------- > > Key: OVIRT-1084 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1084 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Pavel Zhukov > Assignee: infra > Priority: Low > > As per https://ovirt-jira.atlassian.net/browse/OVIRT-970 gerrit and github jobs contan a lot of common code and features so they should be merged and _github_ suffix removed from the job names. -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

[JIRA] (OVIRT-928) check why ost failed on hot plug test while no code got in to break it
by eyal edri [Administrator] (oVirt JIRA) 20 Mar '17

20 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-928?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-928: -------------------------------------------- Resolution: Cannot Reproduce Status: Done (was: To Do) > check why ost failed on hot plug test while no code got in to break it > ---------------------------------------------------------------------- > > Key: OVIRT-928 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-928 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > Labels: ost_failures > > http://jenkins.ovirt.org/view/experimental%20jobs/job/test-repo_ovirt_exper… -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

[JIRA] (OVIRT-926) check why 3.6 experimental job failed even if not error in shown on job
by eyal edri [Administrator] (oVirt JIRA) 20 Mar '17

20 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-926?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-926: ------------------------------------------------- Any updates? Is this still reproducible? > check why 3.6 experimental job failed even if not error in shown on job > ----------------------------------------------------------------------- > > Key: OVIRT-926 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-926 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > Labels: ost_failures > > http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/4322/ > [~gbenhaim@redhat.com][~ngoldin@redhat.com][~ederevea][~bkorren@redhat.com] any ideas? -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

[JIRA] (OVIRT-929) debug why 3.6 ost job failed on vm template test
by eyal edri [Administrator] (oVirt JIRA) 20 Mar '17

20 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-929?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-929: -------------------------------------------- Resolution: Cannot Reproduce Status: Done (was: To Do) > debug why 3.6 ost job failed on vm template test > ------------------------------------------------ > > Key: OVIRT-929 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-929 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > Labels: ost_failures > > http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/4428/consoleF… -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

[JIRA] (OVIRT-1174) deploy-to-experimental job fails when it is triggered by a build-artifacts job that does not create any RPMs
by eyal edri [Administrator] (oVirt JIRA) 20 Mar '17

20 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1174?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1174: --------------------------------------------- Resolution: Won't Fix Status: Done (was: To Do) I think that as long as we don't have valid projects that doesn't produce artifacts we shouldn't fix it. As for containers - we will probably not trigger 'deploy-to-experimental' job anyway and use a different flow. > deploy-to-experimental job fails when it is triggered by a build-artifacts job that does not create any RPMs > ------------------------------------------------------------------------------------------------------------ > > Key: OVIRT-1174 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1174 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > deploy-to-experimental job fails when it is triggered by a build-artifacts job that does not crate any RPMs. It happens because {{repoman}} fails when it doesn't find any RPMs in the Jenkins build that was passed to it. > To solve this we probably just need to make build-artifacts not run deploy-to-experimental at all if no RPMs were created by it. > Here is an example run of deploy-to-experimental that failed because of this: > http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental_master/12473/ -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

[JIRA] (OVIRT-1170) add option to disable networking (or have it off by default)
by eyal edri [Administrator] (oVirt JIRA) 20 Mar '17

20 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1170?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1170: -------------------------------------------------- Do we still need it? If it didn't work out in check-patch, another option is to add an OST test for it. > add option to disable networking (or have it off by default) > ------------------------------------------------------------ > > Key: OVIRT-1170 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1170 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Greg Sheremeta > Assignee: infra > > Add option to disable networking (or have it off by default). Basically, we want to prevent a job from accessing the internet if we want repeatable builds and/or are doing a downstream build somewhere else. Other/downstream build environments often have networking off. Copr has an option: (See: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.… ) > In particular, the ovirt-engine-nodejs-modules build-artifacts job *tries* to stay offline, but an evil node module called 'phantomjs' connects to the internet in a post-offline-install hook. I'd like the option to disallow that and have the build fail. -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

[JIRA] (OVIRT-1193) add on request 'ci help' command via Gerrit
by eyal edri [Administrator] (oVirt JIRA) 20 Mar '17

20 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1193?page=com.atlassian.jira.… ] eyal edri [Administrator] reassigned OVIRT-1193: ------------------------------------------------ Assignee: Daniel Belenky (was: infra) > add on request 'ci help' command via Gerrit > ------------------------------------------- > > Key: OVIRT-1193 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1193 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: Gerrit/git > Reporter: Barak Korren > Assignee: Daniel Belenky > > On 23 February 2017 at 15:10, Martin Sivak <msivak(a)redhat.com> wrote: > > Hi, > > > > do you think it would make sense to send a copy-and-paste ready > > message with help to every new gerrit change? > > > > It could provide all the system test (lago) links, mention the Rerun > > hooks syntax and so on. Just so we do not have to search for it all > > the time? > This is doable, but I think experienced users may find this annoying > it ifs too long. > I'm thinking it may be better to have such a message just suggesting > to type something like '@ci help' to get the full help. > It may even be possible to make it clickable with some trickery rather > then just copy-and-paster ready (I will need to check if its possible > to inject links into Gerrit comments). > Apart from that, Roy offered to write a Gerrit plugin that will add > buttons with the various CI commands. > Adding infra-support to get a Jira ticket opened. > -- > Barak Korren > bkorren(a)redhat.com > RHCE, RHCi, RHV-DevOps Team > https://ifireball.wordpress.com/ -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

[JIRA] (OVIRT-1264) Move individual job definitions from 'jobs/confs/yaml' to 'jobs/confs/projects'
by eyal edri [Administrator] (oVirt JIRA) 20 Mar '17

20 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1264?page=com.atlassian.jira.… ] eyal edri [Administrator] reassigned OVIRT-1264: ------------------------------------------------ Assignee: Daniel Belenky (was: infra) > Move individual job definitions from 'jobs/confs/yaml' to 'jobs/confs/projects' > ------------------------------------------------------------------------------- > > Key: OVIRT-1264 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1264 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: Daniel Belenky > > We've been doing some work recently to enable using the 'jenkins' repo to create different jobs for different Jenkins instances. I had been working on enabling its use to configure the staging server, while Gil had been working on using it downstream. > This work is based on the assumption that the '{{jobs/confs/yaml}}' directory only contains job templates and not individual job definitions. This is certainly true for all standard-CI jobs. > I have found, however, a few jobs that are defined inside the YAML directory. These include: > - ovirt-engine_master_coverity-analysis > - scan_security_and_license_ovirt-engine_master > - system_gerrit-alert-old-patches > - system_jenkins-report > Some of these jobs seem quite old. Can we remove them? Alternatively we could move the definitions to the '{{projects}}' directory, or, ideally, re-factor them into separate 'job-template' and 'project' definitions that reside in the right places. -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

[JIRA] (OVIRT-1084) Merge github and gerrit jobs
by Pavel Zhukov (oVirt JIRA) 20 Mar '17

20 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1084?page=com.atlassian.jira.… ] Pavel Zhukov commented on OVIRT-1084: ------------------------------------- [~eedri] Sorry, I don't understand why we should close this. We still have _github_ suffix in the names and the purpose of this ticket is to get rid of them > Merge github and gerrit jobs > ---------------------------- > > Key: OVIRT-1084 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1084 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Pavel Zhukov > Assignee: infra > Priority: Low > > As per https://ovirt-jira.atlassian.net/browse/OVIRT-970 gerrit and github jobs contan a lot of common code and features so they should be merged and _github_ suffix removed from the job names. -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0