January 2017 - Infra - oVirt List Archives

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4618 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 06 Jan '17

06 Jan '17

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

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4615 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 06 Jan '17

06 Jan '17

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

1 1

[JIRA] (OVIRT-1008) ovirt-srv15 unreachable
by Evgheni Dereveanchin (oVirt JIRA) 06 Jan '17

06 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1008?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1008: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > ovirt-srv15 unreachable > ----------------------- > > Key: OVIRT-1008 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1008 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: Hosting > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > A short time after ovirt-srv15 (one of the Power8 hypervisors) was updated to CentOS 7.3 it went offline. Opening this case to troubleshoot. It was hosting 16 ppc64le Jenkins slaves. We still have slaves running on ovirt-srv16 so this is not critical at the moment. -- This message was sent by Atlassian JIRA (v1000.670.2#100024)

1 0

[JIRA] (OVIRT-1008) ovirt-srv15 unreachable
by Evgheni Dereveanchin (oVirt JIRA) 06 Jan '17

06 Jan '17

Evgheni Dereveanchin created OVIRT-1008: ------------------------------------------- Summary: ovirt-srv15 unreachable Key: OVIRT-1008 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1008 Project: oVirt - virtualization made easy Issue Type: Outage Components: Hosting Reporter: Evgheni Dereveanchin Assignee: infra A short time after ovirt-srv15 (one of the Power8 hypervisors) was updated to CentOS 7.3 it went offline. Opening this case to troubleshoot. It was hosting 16 ppc64le Jenkins slaves. We still have slaves running on ovirt-srv16 so this is not critical at the moment. -- This message was sent by Atlassian JIRA (v1000.670.2#100024)

1 0

oVirt infra daily report - unstable production jobs - 191
by jenkins＠jenkins.phx.ovirt.org 05 Jan '17

05 Jan '17

------=_Part_142_1026887199.1483657266837 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/191//artifact/exported-a… Cheers, Jenkins ------=_Part_142_1026887199.1483657266837 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 - 05/01/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/deploy-to-ovirt_experimental_3.6/">deploy-to-ovirt_experimental_3.6</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/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_3.6_he-system-tests/">ovirt_3.6_he-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_3.6_image-ng-system-tests/">ovirt_3.6_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_4.1_system-tests/">ovirt_4.1_system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_4.0_check-closure_fc23_merged/">repos_4.0_check-closure_fc23_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_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/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_4.1/">test-repo_ovirt_experimental_4.1</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_142_1026887199.1483657266837--

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4605 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 05 Jan '17

05 Jan '17

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

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4601 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 05 Jan '17

05 Jan '17

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

1 2

Re: [ovirt-users] The feature everyone was asking for is finally here...
by Eyal Edri 05 Jan '17

05 Jan '17

I'm not sure I follow how CLI is related to the job, ost is using the ovirt python sdk to run the tests. On Jan 5, 2017 3:36 PM, "Logan Kuhn" <logank(a)wolfram.com> wrote: > Isn't the CLI going away in the semi-near future? > > Regards, > Logan > > ----- On Jan 4, 2017, at 9:31 AM, Eyal Edri <eedri(a)redhat.com> wrote: > > FYI, > > After many requests from multiple developers and testers, the oVirt CI > added a new simple job that lets you run the full fledged end-to-end oVirt > system tests with a click of a button. > You can read all the details and how-to in the new oVirt blog [1]. > > We wanted to allow running oVirt system tests on EVERY open patch from ANY > oVirt project, without relaying on complex building code inside the job. > Luckily we just added the 'build-on-demand' so together with it you can > build any rpms you'd like and use them to run the manual job. > > So the 2 steps you'll need to do are: > > 1. Write 'ci please build' inside a comment on an open oVirt patch ( > make sure the feature is enabled for that project first, its already > available for ovirt-engine,vdsm,dashboard and vdsm-jsonrpc-java) > 2. Run the manual OST job for the version you'd like to test with the > URLs you got from #1 > > You'll get and email once the job is done and you can browse the results > and check for logs from engine and the hosts. > > Please feel free to ask questions on infra(a)ovirt.org as usual. > > > [1] https://www.ovirt.org/blog/2017/01/ovirt-system-tests-to-the-rescue/ > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > > phone: +972-9-7692018 <+972%209-769-2018> > irc: eedri (on #tlv #rhev-dev #rhev-integ) > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > >

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #140 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 05 Jan '17

05 Jan '17

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

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #137 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 05 Jan '17

05 Jan '17

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

1 1