August 2016 - Infra - oVirt List Archives

Jenkins build became unstable: ovirt_3.6_he-system-tests #353
by jenkins＠jenkins.phx.ovirt.org 27 Aug '16

27 Aug '16

See <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/353/changes>

1 1

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

27 Aug '16

------=_Part_80_1698932483.1472252407315 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/58//artifact/exported-ar… Cheers, Jenkins ------=_Part_80_1698932483.1472252407315 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 - 26/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/fabric-ovirt_master_check-merged-el7-x86_64/">fabric-ovirt_master_check-merged-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/fabric-ovirt_master_check-merged-fc23-x86_64/">fabric-ovirt_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> <tr><td> <a href="http://jenkins.ovirt.org/job/mom_3.6_build-artifacts-el7-x86_64/">mom_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/mom_3.6_build-artifacts-fc23-x86_64/">mom_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/mom_4.0_build-artifacts-el7-x86_64/">mom_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/mom_4.0_build-artifacts-fc23-x86_64/">mom_4.0_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/mom_4.0_build-artifacts-fc24-x86_64/">mom_4.0_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/mom_master_build-artifacts-el7-x86_64/">mom_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/mom_master_build-artifacts-fc24-x86_64/">mom_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_3.6.9_check-merged-fc23-x86_64/">ovirt-engine_3.6.9_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-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-optimizer_4.0_build-artifacts-fc23-x86_6…">ovirt-optimizer_4.0_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_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/repos_master_check-closure_merged/">repos_master_check-closure_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/system-backup_jenkins_old_ovirt_org/">system-backup_jenkins_old_ovirt_org</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/">test-repo_ovirt_experimental_3.6</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/vdsm_3.6_build-artifacts-manual-fc23-x86_64/">vdsm_3.6_build-artifacts-manual-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_4.0_build-artifacts-fc23-x86_64/">vdsm_4.0_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/vdsm_4.0_build-artifacts-manual-el7-x86_64/">vdsm_4.0_build-artifacts-manual-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/vdsm_4.0_build-artifacts-manual-fc23-x86_64/">vdsm_4.0_build-artifacts-manual-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_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-manual-el7-x86_64/">vdsm_master_build-artifacts-manual-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/vdsm_master_build-artifacts-manual-fc24-x86_64/">vdsm_master_build-artifacts-manual-fc24-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_80_1698932483.1472252407315--

1 0

Re: [ovirt-devel] Python code style: introducing isort
by Eyal Edri 26 Aug '16

26 Aug '16

Adding infra also, as might be relevant for our code. On Tue, Aug 9, 2016 at 11:06 AM, Sandro Bonazzola <sbonazzo(a)redhat.com> wrote: > Hi, > in project maintained by integration team we tried to adhere to some > styling rules while writing python code, one of these was related to the > import lines. After a lot of time doing this manually, we discovered isort > ( https://pypi.python.org/pypi/isort/4.2.5 ) > > We're using it before we push our code to gerrit and a few days ago I sent > a patch for the python code within ovirt-engine: https://gerrit. > ovirt.org/61964 > > The configuration we're currently using is: > > $ cat ~/.isort.cfg [settings] line_length=79 known_standard_library=configparser,Cheetah.Template > force_single_line=True default_section=FIRSTPARTY known_otopi=otopi > known_host_deploy=ovirt_host_deploy known_ovirt_engine=ovirt_engine > known_ovirt_engine_setup=ovirt_engine_setup known_ovirt_setup_lib=ovirt_setup_lib > known_vdsm=vdsm known_ovirt_hosted_engine_setup=ovirt_hosted_engine_setup > sections=FUTURE,STDLIB,FIRSTPARTY,OTOPI,VDSM,HOST_ > DEPLOY,OVIRT_ENGINE,OVIRT_ENGINE_SETUP,OVIRT_SETUP_LIB, > OVIRT_HOSTED_ENGINE_SETUP,THIRDPARTY,LOCALFOLDER lines_between_types=2 > > It has been proposed to add 'isort --check-only' in check-patch.for python > projects in addition to pep8 style checking. > > It has also been proposed to reach consensus on isort configuration so all > the python code > within ovirt project will have same styling. > > I'd like to get some feedback about these proposal in order to decide how > to procede. > > Thanks, > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > > _______________________________________________ > Devel mailing list > Devel(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel > -- 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)

2 2

otopi based program testing: coverage reports
by Sandro Bonazzola 26 Aug '16

26 Aug '16

The otopi 1.6.0 package currently in ovirt-master-snapshot includes a new feature that allows you to collect coverage reports from your executions. In order to enable the feature you'll need to provide a configuration file like: 8<-------------------------------------- [run] branch = True [report] exclude_lines = # Have to re-enable the standard pragma pragma: no cover # Don't complain about missing debug-only code: def __repr__ if self\.debug # Don't complain if tests don't hit defensive assertion code: raise AssertionError raise NotImplementedError # Don't complain if non-runnable code isn't run: if 0: if __name__ == .__main__.: ignore_errors = True 8<------------------------------------ Be sure to have python-coverage and libselinux-python installed on your system and then execute: OTOPI_COVERAGE=1 COVERAGE_PROCESS_START=<your config> <your command> where your config is the path to your config file and your command may be engine-setup, engine-cleanup, ovirt-host-deploy, hosted-engine --deploy or any other possible command which uses otopi framework. In order to generate the report: coverage html -d coverage_html_report This feature is already leveraged in otopi check-patches and check-merged jobs: http://jenkins.ovirt.org/search/?q=otopi_master_check More test jobs will possibly follow. New tests to improve coverage, improvements to the coverage configuration, suggestions, porting to other projects are welcome. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

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

26 Aug '16

------=_Part_77_255150568.1472166008110 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/57//artifact/exported-ar… Cheers, Jenkins ------=_Part_77_255150568.1472166008110 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 - 25/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/fabric-ovirt_master_check-merged-el7-x86_64/">fabric-ovirt_master_check-merged-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/fabric-ovirt_master_check-merged-fc23-x86_64/">fabric-ovirt_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> <tr><td> <a href="http://jenkins.ovirt.org/job/mom_3.6_build-artifacts-el7-x86_64/">mom_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/mom_3.6_build-artifacts-fc23-x86_64/">mom_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/mom_4.0_build-artifacts-el7-x86_64/">mom_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/mom_4.0_build-artifacts-fc23-x86_64/">mom_4.0_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/mom_4.0_build-artifacts-fc24-x86_64/">mom_4.0_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/mom_master_build-artifacts-el7-x86_64/">mom_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/mom_master_build-artifacts-fc24-x86_64/">mom_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_3.6.9_check-merged-fc23-x86_64/">ovirt-engine_3.6.9_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-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-optimizer_4.0_build-artifacts-fc23-x86_6…">ovirt-optimizer_4.0_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/repos_master_check-closure_merged/">repos_master_check-closure_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/system-backup_jenkins_old_ovirt_org/">system-backup_jenkins_old_ovirt_org</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_3.6_build-artifacts-manual-fc23-x86_64/">vdsm_3.6_build-artifacts-manual-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_4.0_build-artifacts-el7-ppc64le/">vdsm_4.0_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_4.0_build-artifacts-fc23-x86_64/">vdsm_4.0_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/vdsm_4.0_build-artifacts-manual-el7-x86_64/">vdsm_4.0_build-artifacts-manual-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/vdsm_4.0_build-artifacts-manual-fc23-x86_64/">vdsm_4.0_build-artifacts-manual-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_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-manual-el7-x86_64/">vdsm_master_build-artifacts-manual-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/vdsm_master_build-artifacts-manual-fc24-x86_64/">vdsm_master_build-artifacts-manual-fc24-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_77_255150568.1472166008110--

1 0

Re: Change in ovirt-engine[master]: packaging: engine-backup: Create extra users on provisioning
by Yedidyah Bar David 25 Aug '16

25 Aug '16

On Thu, Aug 25, 2016 at 4:12 PM, Jenkins CI <gerrit2(a)gerrit.ovirt.org> wrote: > Jenkins CI has posted comments on this change. > > Change subject: packaging: engine-backup: Create extra users on provisioning > ...................................................................... > > > Patch Set 3: Continuous-Integration-1 > > Build Failed > > http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-4.0_el7_creat… : FAILURE 2016-08-25 13:08:31 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.db.schema plugin.execute:926 execute-output: ['/usr/share/ovirt-engine/dbscripts/schema.sh', '-s', 'localhost', '-p', '5432', '-u', 'engine', '-d', 'engine', '-l', '/var/log/ovirt-engine/setup/ovirt-engine-setup-20160825130745-ak35f1.log', '-c', 'apply'] stderr: psql:/usr/share/ovirt-engine/dbscripts/upgrade/03_05_0580_add_default_instance_types.sql:131: ERROR: duplicate key value violates unique constraint "pk_permissions_id" DETAIL: Key (id)=(00000004-0004-0004-0004-000000000355) already exists. Perhaps push [1] to all active branches? [1] https://gerrit.ovirt.org/62318 > > http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_cr… : SUCCESS > > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/572… : SUCCESS > > -- > To view, visit https://gerrit.ovirt.org/62844 > To unsubscribe, visit https://gerrit.ovirt.org/settings > > Gerrit-MessageType: comment > Gerrit-Change-Id: I61c7d2fd8eee8158434fc4b9df20c965195fdb00 > Gerrit-PatchSet: 3 > Gerrit-Project: ovirt-engine > Gerrit-Branch: master > Gerrit-Owner: Yedidyah Bar David <didi(a)redhat.com> > Gerrit-Reviewer: Jenkins CI > Gerrit-Reviewer: Sandro Bonazzola <sbonazzo(a)redhat.com> > Gerrit-Reviewer: Simone Tiraboschi <stirabos(a)redhat.com> > Gerrit-Reviewer: Yedidyah Bar David <didi(a)redhat.com> > Gerrit-Reviewer: gerrit-hooks <automation(a)ovirt.org> > Gerrit-HasComments: No -- Didi

3 2

[JIRA] (OVIRT-710) export and import vm
by Gal Ben Haim (oVirt JIRA) 25 Aug '16

25 Aug '16

Gal Ben Haim created OVIRT-710: ---------------------------------- Summary: export and import vm Key: OVIRT-710 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-710 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Gal Ben Haim Assignee: infra check in the history of ost for the disabled test -- This message was sent by Atlassian JIRA (v1000.285.1#100011)

1 0

Do we have or can have ppc64 and ppc64le slaves in Jenkins?
by Juan Hernández 25 Aug '16

25 Aug '16

Hello, Some of the packages that I maintain have native components that depend on the underlying processor architecture. Currently we are building these packages only for x86_64. Do we have or can we have ppc64 and ppc64 le Jenkins slaves in order to perform the tests and builds there? Thanks in advance, Juan Hernandez -- Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta 3ºD, 28016 Madrid, Spain Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.

3 10

Build failed in Jenkins: ovirt_4.0_he-system-tests #183
by jenkins＠jenkins.phx.ovirt.org 25 Aug '16

25 Aug '16

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

1 1

Build failed in Jenkins: ovirt_master_publish-rpms_nightly #212
by jenkins＠jenkins.phx.ovirt.org 25 Aug '16

25 Aug '16

See <http://jenkins.ovirt.org/job/ovirt_master_publish-rpms_nightly/212/> ------------------------------------------ Started by user Sandro Bonazzola [EnvInject] - Loading node environment variables. Building on master in workspace <http://jenkins.ovirt.org/job/ovirt_master_publish-rpms_nightly/ws/> [WS-CLEANUP] Deleting project workspace... [workspace] $ /bin/bash -xe /tmp/hudson1630290243355181605.sh + rm -rf <http://jenkins.ovirt.org/job/ovirt_master_publish-rpms_nightly/ws/artifacts> + mkdir <http://jenkins.ovirt.org/job/ovirt_master_publish-rpms_nightly/ws/artifacts> Copied 6 artifacts from "ovirt-host-deploy_master_build-artifacts-el7-x86_64" build number 18 Copied 6 artifacts from "ovirt-host-deploy_master_build-artifacts-fc24-x86_64" build number 8 Copied 8 artifacts from "otopi_master_build-artifacts-el7-x86_64" build number 18 Copied 8 artifacts from "otopi_master_build-artifacts-fc24-x86_64" build number 6 Copied 8 artifacts from "ovirt-vmconsole_master_create-rpms-el7-x86_64_merged" build number 16 Copied 8 artifacts from "ovirt-vmconsole_master_create-rpms-fc24-x86_64_merged" build number 2 Copied 11 artifacts from "ovirt-imageio_master_build-artifacts-el7-x86_64" build number 41 Copied 11 artifacts from "ovirt-imageio_master_build-artifacts-fc24-x86_64" build number 4 Copied 4 artifacts from "ovirt-iso-uploader_master_build-artifacts-el7-x86_64" build number 8 Copied 4 artifacts from "ovirt-iso-uploader_master_build-artifacts-fc24-x86_64" build number 4 Copied 4 artifacts from "ovirt-log-collector_master_build-artifacts-el7-x86_64" build number 9 Copied 4 artifacts from "ovirt-log-collector_master_build-artifacts-fc24-x86_64" build number 5 Copied 4 artifacts from "ovirt-engine-cli_3.6_build-artifacts-el7-x86_64" build number 17 Copied 4 artifacts from "ovirt-engine-cli_3.6_build-artifacts-fc24-x86_64" build number 7 Copied 8 artifacts from "ovirt-engine-extension-aaa-ldap_master_create-rpms-el7-x86_64_merged" build number 16 Copied 8 artifacts from "ovirt-engine-extension-aaa-ldap_master_create-rpms-fc24-x86_64_merged" build number 1 Copied 7 artifacts from "ovirt-engine-extension-aaa-misc_master_create-rpms-el7-x86_64_merged" build number 4 Copied 7 artifacts from "ovirt-engine-extension-aaa-misc_master_create-rpms-fc24-x86_64_merged" build number 1 Copied 7 artifacts from "ovirt-engine-extension-logger-log4j_master_create-rpms-el7-x86_64_merged" build number 4 Copied 7 artifacts from "ovirt-engine-extension-logger-log4j_master_create-rpms-fc24-x86_64_merged" build number 3 Copied 5 artifacts from "ovirt-dwh_master_build-artifacts-el7-x86_64" build number 24 Copied 5 artifacts from "ovirt-dwh_master_build-artifacts-fc24-x86_64" build number 5 Copied 11 artifacts from "ovirt-engine-extension-aaa-jdbc_master_create-rpms-el7-x86_64_merged" build number 6 Copied 7 artifacts from "ovirt-engine-extension-aaa-jdbc_master_create-rpms-fc24-x86_64_merged" build number 1 Copied 4 artifacts from "ovirt-setup-lib_master_build-artifacts-el7-x86_64" build number 6 Copied 4 artifacts from "ovirt-setup-lib_master_build-artifacts-fc24-x86_64" build number 2 Copied 5 artifacts from "vdsm-jsonrpc-java_master_build-artifacts-el7-x86_64" build number 25 Copied 5 artifacts from "vdsm-jsonrpc-java_master_build-artifacts-fc24-x86_64" build number 3 Copied 4 artifacts from "ovirt-engine-sdk_3.6_build-artifacts-el7-x86_64" build number 15 Copied 4 artifacts from "ovirt-engine-sdk_3.6_build-artifacts-fc24-x86_64" build number 4 Copied 7 artifacts from "ovirt-engine-sdk_master_build-artifacts-el7-x86_64" build number 44 Copied 8 artifacts from "ovirt-engine-sdk_master_build-artifacts-fc24-x86_64" build number 19 Copied 7 artifacts from "ovirt-engine-sdk-java_3.6_create-rpms-el7-x86_64_merged" build number 10 Copied 7 artifacts from "ovirt-engine-sdk-java_3.6_create-rpms-fc24-x86_64_merged" build number 4 Copied 4 artifacts from "ovirt-engine-sdk-java_master_build-artifacts-el7-x86_64" build number 35 Copied 4 artifacts from "ovirt-engine-sdk-java_master_build-artifacts-fc24-x86_64" build number 18 Copied 4 artifacts from "ovirt-image-uploader_master_build-artifacts-el7-x86_64" build number 10 Copied 4 artifacts from "ovirt-image-uploader_master_build-artifacts-fc24-x86_64" build number 4 Copied 4 artifacts from "ovirt-scheduler-proxy_master_build-artifacts-el7-x86_64" build number 5 Copied 4 artifacts from "ovirt-scheduler-proxy_master_build-artifacts-fc24-x86_64" build number 1 Copied 6 artifacts from "ovirt-optimizer_master_build-artifacts-el7-x86_64" build number 9 Copied 7 artifacts from "ovirt-optimizer_master_build-artifacts-fc24-x86_64" build number 8 Copied 5 artifacts from "ovirt-jboss-modules-maven-plugin_master_build-artifacts-el7-x86_64" build number 3 Copied 5 artifacts from "ovirt-jboss-modules-maven-plugin_master_build-artifacts-fc24-x86_64" build number 2 Copied 4 artifacts from "ovirt-engine-dashboard_master_build-artifacts-el7-x86_64" build number 59 Copied 4 artifacts from "ovirt-engine-dashboard_master_build-artifacts-fc24-x86_64" build number 29 Copied 6 artifacts from "ioprocess_master_build-artifacts-el7-x86_64" build number 41 Copied 6 artifacts from "ioprocess_master_build-artifacts-fc24-x86_64" build number 4 Copied 6 artifacts from "ioprocess_master_build-artifacts-el7-ppc64le" build number 4 Copied 6 artifacts from "ioprocess_master_build-artifacts-fc24-ppc64le" build number 4 Copied 49 artifacts from "vdsm_master_build-artifacts-el7-x86_64" build number 735 Copied 49 artifacts from "vdsm_master_build-artifacts-fc24-x86_64" build number 226 Copied 7 artifacts from "ovirt-hosted-engine-ha_master_create-rpms-el7-x86_64_merged" build number 24 Copied 7 artifacts from "ovirt-hosted-engine-ha_master_create-rpms-fc24-x86_64_merged" build number 8 Copied 4 artifacts from "ovirt-hosted-engine-setup_master_build-artifacts-el7-x86_64" build number 53 Copied 4 artifacts from "ovirt-hosted-engine-setup_master_build-artifacts-fc24-x86_64" build number 14 Copied 13 artifacts from "qemu_master_create-rpms-el7-x86_64_merged" build number 7 Copied 13 artifacts from "qemu_master_create-rpms-el7-ppc64le_merged" build number 7 Copied 7 artifacts from "unboundid-ldapsdk_master_create-rpms-el7-x86_64_merged" build number 3 Copied 6 artifacts from "ovirt-appliance_master_build-artifacts-el7-x86_64" build number 150 Copied 25 artifacts from "ovirt-engine_master_build-artifacts-el7-x86_64" build number 575 Copied 25 artifacts from "ovirt-engine_master_build-artifacts-fc24-x86_64" build number 279 Copied 6 artifacts from "mom_master_create-rpms-el7-x86_64_merged" build number 11 Copied 6 artifacts from "mom_master_create-rpms-fc24-x86_64_merged" build number 3 Copied 9 artifacts from "ovirt-live_master_build-artifacts-el7-x86_64" build number 25 Copied 9 artifacts from "ovirt-live_master_build-artifacts-fc24-x86_64" build number 14 Copied 6 artifacts from "py2exe-py2.7_master_create-rpms-fc24-x86_64_merged" build number 1 Copied 6 artifacts from "pywin32-py2.7_master_create-rpms-fc24-x86_64_merged" build number 1 Copied 6 artifacts from "python-windows_master_create-rpms-fc24-x86_64_merged" build number 1 Copied 6 artifacts from "vcredist-x86_master_create-rpms-fc24-x86_64_merged" build number 1 Copied 6 artifacts from "nsis-simple-service-plugin_master_create-rpms-fc24-x86_64_merged" build number 1 Copied 7 artifacts from "ovirt-wgt_master_create-rpms-fc24-x86_64_merged" build number 3 Copied 4 artifacts from "cockpit-ovirt_master_build-artifacts-el7-x86_64" build number 105 Copied 4 artifacts from "cockpit-ovirt_master_build-artifacts-fc24-x86_64" build number 14 Copied 7 artifacts from "ovirt-engine-sdk-ruby_master_build-artifacts-el7-x86_64" build number 42 Copied 7 artifacts from "ovirt-engine-sdk-ruby_master_build-artifacts-fc24-x86_64" build number 19 Copied 8 artifacts from "ovirt-release_master_build-artifacts-el7-x86_64" build number 109 Copied 3 artifacts from "imgbased_master_build-artifacts-el7-x86_64" build number 87 ERROR: Unable to find project for artifact copy: ovirt-node-ng_master_build-artifacts-fc22-x86_64_archived_for_deletion This may be due to incorrect project name or permission settings; see help for project name in job configuration.

1 1