- Infra - oVirt List Archives

[JIRA] (OVIRT-869) Investigate proxy errors from proxy.phx.ovirt.org
by Barak Korren (oVirt JIRA) 27 Nov '16

27 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-869?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-869: ------------------------------------ {quote} It currently has :127.0.0.1 proxy.phx.ovirt.org Do you mean adding the public IP address as well? {quote} If it has this already then the error is strange indeed, all I can think of is that maybe the mock environment running the failed job was not configured correctly (Trying to use the proxy repo URLs without setting it up as an HTTP proxy _in addition to_ not having proper _DNS_ config. If it was justh the HTTP proxy setting I would expect to see a "_connection refused_" error rather then "_could not resolve_"). {quote} By full fledged mirrors you mean have it on resources.ovirt.org ? will we need Katello to manage them or mirror with rsync will suffice? {quote} Not necessarily on resources.ovirt.org, we could (and maybe should) use a different server for that. WRT the mirroring solution itself we have many options with varying degrees of automation, features and required effort: # rsync (though not all upsreams may allow this kind of access) # yum reposync # repoman # Pulp # Artifactory # Katello The benefit of Katello would be in allowing us to control exactly which packages get tested by leveraging the work flow environments and the content views, but we could build comparable solutions with other tools. > Investigate proxy errors from proxy.phx.ovirt.org > ------------------------------------------------- > > Key: OVIRT-869 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-869 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: Highest > > We need to make sure jobs don't fail on proxy like [1]. > Either use original repos if proxy is down or add watchdog / alerts for the proxy service. > http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/3693/artif… -- This message was sent by Atlassian JIRA (v1000.571.2#100021)

1 0

Re: Change in ovirt-engine[master]: core: improving vms_with_tags view performance
by Martin Perina 27 Nov '16

27 Nov '16

Could you please take a look at upgrade from 3.6 job? Following error seems to me like an CI infra issue: error: could not apply 8525684... Modified cleanup.sh in 'upgrade_to_4.0' Thanks Martin On Fri, Nov 25, 2016 at 6:54 PM, Code Review <gerrit(a)ovirt.org> wrote: > From Jenkins CI: > > Jenkins CI has posted comments on this change. > > Change subject: core: improving vms_with_tags view performance > ...................................................................... > > > Patch Set 4: > > Build Failed > > http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade- > from-3.6_el7_merged/1039/ : FAILURE > > http://jenkins.ovirt.org/job/ovirt-engine_master_check- > merged-el7-x86_64/2650/ : SUCCESS > > http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade- > from-4.0_el7_merged/2183/ : SUCCESS > > http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade- > from-master_el7_merged/2657/ : SUCCESS > > http://jenkins.ovirt.org/job/ovirt-engine_master_check- > merged-fc24-x86_64/1753/ : SUCCESS > > -- > To view, visit https://gerrit.ovirt.org/66165 > To unsubscribe, visit https://gerrit.ovirt.org/settings > > Gerrit-MessageType: comment > Gerrit-Change-Id: Ib5a6637b7c890e445940c8d0a770c2bd7e11e72b > Gerrit-PatchSet: 4 > Gerrit-Project: ovirt-engine > Gerrit-Branch: master > Gerrit-Owner: Eli Mesika <emesika(a)redhat.com> > Gerrit-Reviewer: Arik Hadas <ahadas(a)redhat.com> > Gerrit-Reviewer: Eli Mesika <emesika(a)redhat.com> > Gerrit-Reviewer: Jenkins CI > Gerrit-Reviewer: Martin Peřina <mperina(a)redhat.com> > Gerrit-Reviewer: gerrit-hooks <automation(a)ovirt.org> > Gerrit-HasComments: No >

2 1

[JIRA] (OVIRT-869) Investigate proxy errors from proxy.phx.ovirt.org
by eyal edri [Administrator] (oVirt JIRA) 27 Nov '16

27 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-869?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-869: ------------------------------------------------- bq. Port 5000 is where the python script is running no? So the Squid had an issue resolving the name of the very host it is running on? We should probably just resolve this forever by placing the name in /etc/hosts on the proxy server.... It currently has :127.0.0.1 proxy.phx.ovirt.org Do you mean adding the public IP address as well? bq. Typically the failures we're seeing are because of failures in the origin mirror we are actually proxying (Fedora and EPEL seem to be notoriously non-atomic when updating their mirrors). The way to solve this is only to used fully-fledged mirrors instead of a proxy (But this takes more maintenance and more storage). By full fledged mirrors you mean have it on resources.ovirt.org ? will we need Katello to manage them or mirror with rsync will suffice? > Investigate proxy errors from proxy.phx.ovirt.org > ------------------------------------------------- > > Key: OVIRT-869 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-869 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: Highest > > We need to make sure jobs don't fail on proxy like [1]. > Either use original repos if proxy is down or add watchdog / alerts for the proxy service. > http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/3693/artif… -- This message was sent by Atlassian JIRA (v1000.571.2#100021)

1 0

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

27 Nov '16

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

1 1

[JIRA] (OVIRT-869) Investigate proxy errors from proxy.phx.ovirt.org
by Barak Korren (oVirt JIRA) 27 Nov '16

27 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-869?page=com.atlassian.jira.p… ] Barak Korren edited comment on OVIRT-869 at 11/27/16 10:50 AM: --------------------------------------------------------------- The error seems to be a DNS error: {code} DEBUG util.py:421: http://proxy.phx.ovirt.org:5000/centos-base/7/x86_64/Packages/unzip-6.0-15.…: [Errno 14] curl#5 - "Could not resolve proxy: proxy.phx.ovirt.org" {code} Port 5000 is where the python script is running no? So the Squid had an issue resolving the name of the very host it is running on? We should probably just resolve this forever by placing the name in {{/etc/hosts}} on the proxy server.... {quote} Either use original repos if proxy is down or add watchdog / alerts for the proxy service. {quote} We have this: # {{mock_runner.sh}} tries to contact proxy and uses un-proxyed configuration if it fails (This is why it has both {{\*.cnf}} and {{*-proxy.cnf}} files) # There is a cron job watchdog running on the proxy itself and restarting it # AFAIK we also have Icinga monitoring it. Typically the failures we're seeing are because of failures in the origin mirror we are actually proxying (Fedora and EPEL seem to be notoriously non-atomic when updating their mirrors). The way to solve this is only to used fully-fledged mirrors instead of a proxy (But this takes more maintenance and more storage). was (Author: bkorren(a)redhat.com) The error seems to be a DNS error: {code} DEBUG util.py:421: http://proxy.phx.ovirt.org:5000/centos-base/7/x86_64/Packages/unzip-6.0-15.…: [Errno 14] curl#5 - "Could not resolve proxy: proxy.phx.ovirt.org" {code} Port 5000 is where the python script is running no? So the Squid had an issue resolving the name of the very host it is running on? We should probably just resolve this forever by placing the name in {{/etc/hosts}} on the proxy server.... {code} Either use original repos if proxy is down or add watchdog / alerts for the proxy service. {code} We have this: # {{mock_runner.sh}} tries to contact proxy and uses un-proxyed configuration if it fails (This is why it has both {{\*.cnf}} and {{*-proxy.cnf}} files) # There is a cron job watchdog running on the proxy itself and restarting it # AFAIK we also have Icinga monitoring it. Typically the failures we're seeing are because of failures in the origin mirror we are actually proxying (Fedora and EPEL seem to be notoriously non-atomic when updating their mirrors). The way to solve this is only to used fully-fledged mirrors instead of a proxy (But this takes more maintenance and more storage). > Investigate proxy errors from proxy.phx.ovirt.org > ------------------------------------------------- > > Key: OVIRT-869 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-869 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: Highest > > We need to make sure jobs don't fail on proxy like [1]. > Either use original repos if proxy is down or add watchdog / alerts for the proxy service. > http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/3693/artif… -- This message was sent by Atlassian JIRA (v1000.571.2#100021)

1 0

[JIRA] (OVIRT-869) Investigate proxy errors from proxy.phx.ovirt.org
by Barak Korren (oVirt JIRA) 27 Nov '16

27 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-869?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-869: ------------------------------------ The error seems to be a DNS error: {code} DEBUG util.py:421: http://proxy.phx.ovirt.org:5000/centos-base/7/x86_64/Packages/unzip-6.0-15.…: [Errno 14] curl#5 - "Could not resolve proxy: proxy.phx.ovirt.org" {code} Port 5000 is where the python script is running no? So the Squid had an issue resolving the name of the very host it is running on? We should probably just resolve this forever by placing the name in {{/etc/hosts}} on the proxy server.... {code} Either use original repos if proxy is down or add watchdog / alerts for the proxy service. {code} We have this: # {{mock_runner.sh}} tries to contact proxy and uses un-proxyed configuration if it fails (This is why it has both {{\*.cnf}} and {{*-proxy.cnf}} files) # There is a cron job watchdog running on the proxy itself and restarting it # AFAIK we also have Icinga monitoring it. Typically the failures we're seeing are because of failures in the origin mirror we are actually proxying (Fedora and EPEL seem to be notoriously non-atomic when updating their mirrors). The way to solve this is only to used fully-fledged mirrors instead of a proxy (But this takes more maintenance and more storage). > Investigate proxy errors from proxy.phx.ovirt.org > ------------------------------------------------- > > Key: OVIRT-869 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-869 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: Highest > > We need to make sure jobs don't fail on proxy like [1]. > Either use original repos if proxy is down or add watchdog / alerts for the proxy service. > http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/3693/artif… -- This message was sent by Atlassian JIRA (v1000.571.2#100021)

1 0

[JIRA] (OVIRT-869) Investigate proxy errors from proxy.phx.ovirt.org
by eyal edri [Administrator] (oVirt JIRA) 27 Nov '16

27 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-869?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-869: ------------------------------------------------- also, add any needed into to infra docs on troubleshooting errors > Investigate proxy errors from proxy.phx.ovirt.org > ------------------------------------------------- > > Key: OVIRT-869 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-869 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: Highest > > We need to make sure jobs don't fail on proxy like [1]. > Either use original repos if proxy is down or add watchdog / alerts for the proxy service. > http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/3693/artif… -- This message was sent by Atlassian JIRA (v1000.571.2#100021)

1 0

[JIRA] (OVIRT-869) Investigate proxy errors from proxy.phx.ovirt.org
by eyal edri [Administrator] (oVirt JIRA) 27 Nov '16

27 Nov '16

eyal edri [Administrator] created OVIRT-869: ----------------------------------------------- Summary: Investigate proxy errors from proxy.phx.ovirt.org Key: OVIRT-869 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-869 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: eyal edri [Administrator] Assignee: infra Priority: Highest We need to make sure jobs don't fail on proxy like [1]. Either use original repos if proxy is down or add watchdog / alerts for the proxy service. http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/3693/artif… -- This message was sent by Atlassian JIRA (v1000.571.2#100021)

1 0

[JIRA] (OVIRT-869) Investigate proxy errors from proxy.phx.ovirt.org
by eyal edri [Administrator] (oVirt JIRA) 27 Nov '16

27 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-869?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-869: -------------------------------------------- Epic Link: OVIRT-403 > Investigate proxy errors from proxy.phx.ovirt.org > ------------------------------------------------- > > Key: OVIRT-869 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-869 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: Highest > > We need to make sure jobs don't fail on proxy like [1]. > Either use original repos if proxy is down or add watchdog / alerts for the proxy service. > http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/3693/artif… -- This message was sent by Atlassian JIRA (v1000.571.2#100021)

1 0

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

27 Nov '16

------=_Part_1002_32509470.1480201208132 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/150//artifact/exported-a… Cheers, Jenkins ------=_Part_1002_32509470.1480201208132 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/11/2016 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Jobs (Production)</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/cockpit-ovirt_ovirt-4.1_build-artifacts-fc23-x…">cockpit-ovirt_ovirt-4.1_build-artifacts-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/fabric-ovirt_master_check-merged-el7-x86_64/">fabric-ovirt_master_check-merged-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86…">ovirt-appliance_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-engine-api-explorer_master_build-artifac…">ovirt-engine-api-explorer_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-engine-api-explorer_master_build-artifac…">ovirt-engine-api-explorer_master_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-engine_3.6_build-artifacts-el6-x86_64/">ovirt-engine_3.6_build-artifacts-el6-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-engine_3.6_build-artifacts-el7-x86_64/">ovirt-engine_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-engine_3.6_build-artifacts-fc23-x86_64/">ovirt-engine_3.6_build-artifacts-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-engine_4.0_build-artifacts-el7-x86_64/">ovirt-engine_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-engine_4.0_build-artifacts-fc23-x86_64/">ovirt-engine_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-engine_master_upgrade-from-3.6_el7_merge…">ovirt-engine_master_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-guest-agent_master_build-artifacts-fc23-…">ovirt-guest-agent_master_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-live_master_experimental_create-iso-el7-…">ovirt-live_master_experimental_create-iso-el7-x86_64</a> </td><td> <h3>This job generates a nightly iso of ovirt-live using experimental repos</h3> </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6…">ovirt-node-ng_master_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-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-node-ng_ovirt-master-experimental_build-…">ovirt-node-ng_ovirt-master-experimental_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-provider-ovn_master_build-artifacts-el7-…">ovirt-provider-ovn_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-provider-ovn_master_check-merged-el7-x86…">ovirt-provider-ovn_master_check-merged-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_system-tests_debug/">ovirt_master_system-tests_debug</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_master_check-closure_fc24_merged/">repos_master_check-closure_fc24_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/vdsm_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> ------=_Part_1002_32509470.1480201208132--

1 0