February 2018 - Infra - oVirt List Archives

[JIRA] (OVIRT-1887) Document STDCI DSL
by Daniel Belenky (oVirt JIRA) 07 Feb '18

07 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1887?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-1887: ------------------------------------- Assignee: Daniel Belenky (was: infra) Component/s: oVirt CI Epic Link: OVIRT-400 Description: Write E2E documentation for STDCI DSL > Document STDCI DSL > ------------------ > > Key: OVIRT-1887 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1887 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Daniel Belenky > Assignee: Daniel Belenky > Labels: standard-ci > > Write E2E documentation for STDCI DSL -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

[JIRA] (OVIRT-1887) Document STDCI DSL
by Daniel Belenky (oVirt JIRA) 07 Feb '18

07 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1887?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-1887: ---------------------------------- Labels: standard-ci (was: ) > Document STDCI DSL > ------------------ > > Key: OVIRT-1887 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1887 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Daniel Belenky > Assignee: infra > Labels: standard-ci > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

[JIRA] (OVIRT-1887) Document STDCI DSL
by Daniel Belenky (oVirt JIRA) 07 Feb '18

07 Feb '18

Daniel Belenky created OVIRT-1887: ------------------------------------- Summary: Document STDCI DSL Key: OVIRT-1887 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1887 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Daniel Belenky Assignee: infra -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

[oVirt CI] standard-enqueue - Build #9761 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 07 Feb '18

07 Feb '18

------=_Part_128_647837091.1518004641839 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/standard-enqueue/9761/ Build Name: #9761 Build Description: Gerrit: 69504 - ovirt-engine-cli (3.6, 4.1, 4.2, master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/69504 - title: cli: Fix SDK dependency - project: ovirt-engine-cli - branch: cli_3.6 - author: Juan Hernandez <juan.hernandez(a)redhat.com> ------=_Part_128_647837091.1518004641839--

1 0

[CQ]: 87060, 2 (ovirt-hosted-engine-setup) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Feb '18

07 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87060,2 (ovirt-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 86910,1 (ovirt-hosted-engine-setup) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86910,1 (ovirt-hosted-engine- setup) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87060/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86910/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/578/

1 0

[CQ]: 87235, 2 (ovirt-hosted-engine-setup) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Feb '18

07 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87235,2 (ovirt-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 86910,1 (ovirt-hosted-engine-setup) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86910,1 (ovirt-hosted-engine- setup) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87235/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86910/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/576/

1 0

[CQ]: 87230, 2 (ovirt-hosted-engine-setup) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Feb '18

07 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87230,2 (ovirt-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 86910,1 (ovirt-hosted-engine-setup) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86910,1 (ovirt-hosted-engine- setup) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87230/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86910/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/575/

1 0

[JIRA] (OVIRT-1886) Add fcraw support for s390x and ppc64le
by sbonazzo (oVirt JIRA) 07 Feb '18

07 Feb '18

This is a multi-part message in MIME format... ------------=_1517999829-27008-209 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1886?page=com.atlassian.jira.… ] sbonazzo commented on OVIRT-1886: --------------------------------- Please push a revert for https://gerrit.ovirt.org/87249 once fcraw mock runner supports ppc64le and s390x > Add fcraw support for s390x and ppc64le > --------------------------------------- > > Key: OVIRT-1886 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1886 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Hi, > pushed https://gerrit.ovirt.org/#/c/87068/ for adding support to fcraw for > s390x ad ppc64le but looks like it won't be enough, opening a ticket as > suggested by Barak. > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1517999829-27008-209 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1886?page=com.atlassian.jira.… ]</pre> <h3>sbonazzo commented on OVIRT-1886:</h3> <p>Please push a revert for <a href="https://gerrit.ovirt.org/87249">https://gerrit.ovirt.org/87249</a> once fcraw mock runner supports ppc64le and s390x</p> <blockquote><h3>Add fcraw support for s390x and ppc64le</h3> <pre> Key: OVIRT-1886 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1886 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra</pre> <p>Hi, pushed <a href="https://gerrit.ovirt.org/#/c/87068/">https://gerrit.ovirt.org/#/c/87068/</a> for adding support to fcraw for s390x ad ppc64le but looks like it won't be enough, opening a ticket as suggested by Barak. — SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <<a href="https://www.redhat.com/">https://www.redhat.com/</a>> <<a href="https://red.ht/sig">https://red.ht/sig</a>> TRIED. TESTED. TRUSTED. <<a href="https://redhat.com/trusted">https://redhat.com/trusted</a>></p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1517999829-27008-209--

1 0

[JIRA] (OVIRT-1886) Add fcraw support for s390x and ppc64le
by sbonazzo (oVirt JIRA) 07 Feb '18

07 Feb '18

This is a multi-part message in MIME format... ------------=_1517999673-22392-277 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit sbonazzo created OVIRT-1886: ------------------------------- Summary: Add fcraw support for s390x and ppc64le Key: OVIRT-1886 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1886 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra Hi, pushed https://gerrit.ovirt.org/#/c/87068/ for adding support to fcraw for s390x ad ppc64le but looks like it won't be enough, opening a ticket as suggested by Barak. -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1517999673-22392-277 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>sbonazzo created OVIRT-1886:</h3> <pre> Summary: Add fcraw support for s390x and ppc64le Key: OVIRT-1886 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1886 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra</pre> <p>Hi, pushed <a href="https://gerrit.ovirt.org/#/c/87068/">https://gerrit.ovirt.org/#/c/87068/</a> for adding support to fcraw for s390x ad ppc64le but looks like it won't be enough, opening a ticket as suggested by Barak.</p> <p>—</p> <p>SANDRO BONAZZOLA</p> <p>ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D</p> <p>Red Hat EMEA <<a href="https://www.redhat.com/">https://www.redhat.com/</a>> <<a href="https://red.ht/sig">https://red.ht/sig</a>> TRIED. TESTED. TRUSTED. <<a href="https://redhat.com/trusted">https://redhat.com/trusted</a>></p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1517999673-22392-277--

1 0

[CQ]: 85665, 12 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Feb '18

07 Feb '18

A system test invoked by the "ovirt-master" change queue including change 85665,12 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 87181,2 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87181,2 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/85665/12 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87181/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5326/

1 0

[CQ]: 86462, 4 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Feb '18

07 Feb '18

A system test invoked by the "ovirt-master" change queue including change 86462,4 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 87181,2 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87181,2 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/86462/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87181/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5321/

1 0

[JIRA] (OVIRT-1885) Remove slave/resource management from Jenkins
by Barak Korren (oVirt JIRA) 07 Feb '18

07 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1885?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1885: -------------------------------- Epic Link: OVIRT-400 > Remove slave/resource management from Jenkins > --------------------------------------------- > > Key: OVIRT-1885 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1885 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Master, Jenkins Slaves > Reporter: Barak Korren > Assignee: infra > Labels: scale > > The way out infra is configure right now, resource allocation and management is done by Jenkins itself. This means that all resources need to pre-allocated to Jenkins in the form of slaves. > If we want to have separate Jenkins masters, our current configuration will force us to hard-split the resources between different Jenkins masters. > If we want to share our pool of resources between multiple masters, it means that resource allocation needs to move out of Jenkins to external tools. > Potential tools for different types of resources are: > * Beaker for managing physical hosts > * oVirt + a Jenkins could provider plugin for managing VMs > * OpenShift for managing containers (As a replacement for chroots). -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

[JIRA] (OVIRT-1885) Remove slave/resource management from Jenkins
by Barak Korren (oVirt JIRA) 07 Feb '18

07 Feb '18

Barak Korren created OVIRT-1885: ----------------------------------- Summary: Remove slave/resource management from Jenkins Key: OVIRT-1885 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1885 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Master, Jenkins Slaves Reporter: Barak Korren Assignee: infra The way out infra is configure right now, resource allocation and management is done by Jenkins itself. This means that all resources need to pre-allocated to Jenkins in the form of slaves. If we want to have separate Jenkins masters, our current configuration will force us to hard-split the resources between different Jenkins masters. If we want to share our pool of resources between multiple masters, it means that resource allocation needs to move out of Jenkins to external tools. Potential tools for different types of resources are: * Beaker for managing physical hosts * oVirt + a Jenkins could provider plugin for managing VMs * OpenShift for managing containers (As a replacement for chroots). -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

[JIRA] (OVIRT-1884) Scale up to multipile Jenkins masters
by Barak Korren (oVirt JIRA) 07 Feb '18

07 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1884?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1884: ----------------------------------- Assignee: Barak Korren (was: infra) > Scale up to multipile Jenkins masters > ------------------------------------- > > Key: OVIRT-1884 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1884 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Master > Reporter: Barak Korren > Assignee: Barak Korren > Labels: scale > > There are several reasons why we would like to enable scaling up to multiple Jenkins masters: > * We may reach a point where a single jenkins master will simple not be able to cope with the workload we have - this is especially true as we increase our use of heavy features like pipelines and blue ocean. > * If we choose to start using OpenShift's embedded Jenkins, the approach there is that every project gets its own Jenkins instance. > * As we increase out reach and support more projects, some of them would not like to use an oVirt branded Jenkins instance. > This ticket would track the work we need to do to enable supporting multiple Jenkins master in out infra. Individual pieces of work should be created as separate tickets and be linked as blockers to this one. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

[JIRA] (OVIRT-1884) Scale up to multipile Jenkins masters
by Barak Korren (oVirt JIRA) 07 Feb '18

07 Feb '18

This is a multi-part message in MIME format... ------------=_1517996808-26764-286 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Barak Korren created OVIRT-1884: ----------------------------------- Summary: Scale up to multipile Jenkins masters Key: OVIRT-1884 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1884 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Master Reporter: Barak Korren Assignee: infra There are several reasons why we would like to enable scaling up to multiple Jenkins masters: * We may reach a point where a single jenkins master will simple not be able to cope with the workload we have - this is especially true as we increase our use of heavy features like pipelines and blue ocean. * If we choose to start using OpenShift's embedded Jenkins, the approach there is that every project gets its own Jenkins instance. * As we increase out reach and support more projects, some of them would not like to use an oVirt branded Jenkins instance. This ticket would track the work we need to do to enable supporting multiple Jenkins master in out infra. Individual pieces of work should be created as separate tickets and be linked as blockers to this one. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1517996808-26764-286 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Barak Korren created OVIRT-1884:</h3> <pre> Summary: Scale up to multipile Jenkins masters Key: OVIRT-1884 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1884 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Master Reporter: Barak Korren Assignee: infra</pre> <p>There are several reasons why we would like to enable scaling up to multiple Jenkins masters:</p> <ul><li><p>We may reach a point where a single jenkins master will simple not be able to cope with the workload we have – this is especially true as we increase our use of heavy features like pipelines and blue ocean.</p></li> <li><p>If we choose to start using OpenShift's embedded Jenkins, the approach there is that every project gets its own Jenkins instance.</p></li> <li><p>As we increase out reach and support more projects, some of them would not like to use an oVirt branded Jenkins instance.</p></li></ul> <p>This ticket would track the work we need to do to enable supporting multiple Jenkins master in out infra. Individual pieces of work should be created as separate tickets and be linked as blockers to this one.</p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1517996808-26764-286--

1 0

[JIRA] (OVIRT-1884) Scale up to multipile Jenkins masters
by Barak Korren (oVirt JIRA) 07 Feb '18

07 Feb '18

This is a multi-part message in MIME format... ------------=_1517996808-12609-300 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1884?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1884: -------------------------------- Epic Link: OVIRT-400 > Scale up to multipile Jenkins masters > ------------------------------------- > > Key: OVIRT-1884 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1884 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Master > Reporter: Barak Korren > Assignee: infra > Labels: scale > > There are several reasons why we would like to enable scaling up to multiple Jenkins masters: > * We may reach a point where a single jenkins master will simple not be able to cope with the workload we have - this is especially true as we increase our use of heavy features like pipelines and blue ocean. > * If we choose to start using OpenShift's embedded Jenkins, the approach there is that every project gets its own Jenkins instance. > * As we increase out reach and support more projects, some of them would not like to use an oVirt branded Jenkins instance. > This ticket would track the work we need to do to enable supporting multiple Jenkins master in out infra. Individual pieces of work should be created as separate tickets and be linked as blockers to this one. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1517996808-12609-300 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1884?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1884:</h3> <pre>Epic Link: OVIRT-400</pre> <blockquote><h3>Scale up to multipile Jenkins masters</h3> <pre> Key: OVIRT-1884 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1884 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Master Reporter: Barak Korren Assignee: infra Labels: scale</pre> <p>There are several reasons why we would like to enable scaling up to multiple Jenkins masters:</p> <ul><li><p>We may reach a point where a single jenkins master will simple not be able to cope with the workload we have – this is especially true as we increase our use of heavy features like pipelines and blue ocean.</p></li> <li><p>If we choose to start using OpenShift's embedded Jenkins, the approach there is that every project gets its own Jenkins instance.</p></li> <li><p>As we increase out reach and support more projects, some of them would not like to use an oVirt branded Jenkins instance.</p></li></ul> <p>This ticket would track the work we need to do to enable supporting multiple Jenkins master in out infra. Individual pieces of work should be created as separate tickets and be linked as blockers to this one.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1517996808-12609-300--

1 0

[CQ]: 86521, 1 (ovirt-engine-sdk-ruby) failed "ovirt-master" system tests
by oVirt Jenkins 07 Feb '18

07 Feb '18

Change 86521,1 (ovirt-engine-sdk-ruby) is probably the reason behind recent system test failures in the "ovirt-master" 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: https://gerrit.ovirt.org/#/c/86521/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5316/

1 0

[JIRA] (OVIRT-1883) Figure out how to make caches work with re-provisioned hosts (E.g. from beaker)
by Barak Korren (oVirt JIRA) 07 Feb '18

07 Feb '18

This is a multi-part message in MIME format... ------------=_1517995716-25255-216 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1883?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1883: ----------------------------------- Assignee: Barak Korren (was: infra) > Figure out how to make caches work with re-provisioned hosts (E.g. from beaker) > ------------------------------------------------------------------------------- > > Key: OVIRT-1883 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1883 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Slaves > Reporter: Barak Korren > Assignee: Barak Korren > Labels: beaker > > The CI system currently relies on the fact that the Jenkins slaves are stateful, and stores various caches on them. > If we move to a mechanism where slaves are provisioned dynamically, we need to consider ho to keep having effective caches. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1517995716-25255-216 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1883?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren reassigned OVIRT-1883:</h3> <pre>Assignee: Barak Korren (was: infra)</pre> <blockquote><h3>Figure out how to make caches work with re-provisioned hosts (E.g. from beaker)</h3> <pre> Key: OVIRT-1883 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1883 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Slaves Reporter: Barak Korren Assignee: Barak Korren Labels: beaker</pre> <p>The CI system currently relies on the fact that the Jenkins slaves are stateful, and stores various caches on them. If we move to a mechanism where slaves are provisioned dynamically, we need to consider ho to keep having effective caches.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1517995716-25255-216--

1 0

[JIRA] (OVIRT-1883) Figure out how to make caches work with re-provisioned hosts (E.g. from beaker)
by Barak Korren (oVirt JIRA) 07 Feb '18

07 Feb '18

This is a multi-part message in MIME format... ------------=_1517995701-11810-157 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1883?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1883: -------------------------------- Epic Link: OVIRT-400 > Figure out how to make caches work with re-provisioned hosts (E.g. from beaker) > ------------------------------------------------------------------------------- > > Key: OVIRT-1883 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1883 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Slaves > Reporter: Barak Korren > Assignee: infra > Labels: beaker > > The CI system currently relies on the fact that the Jenkins slaves are stateful, and stores various caches on them. > If we move to a mechanism where slaves are provisioned dynamically, we need to consider ho to keep having effective caches. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1517995701-11810-157 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1883?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1883:</h3> <pre>Epic Link: OVIRT-400</pre> <blockquote><h3>Figure out how to make caches work with re-provisioned hosts (E.g. from beaker)</h3> <pre> Key: OVIRT-1883 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1883 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Slaves Reporter: Barak Korren Assignee: infra Labels: beaker</pre> <p>The CI system currently relies on the fact that the Jenkins slaves are stateful, and stores various caches on them. If we move to a mechanism where slaves are provisioned dynamically, we need to consider ho to keep having effective caches.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1517995701-11810-157--

1 0

[JIRA] (OVIRT-1883) Figure out how to make caches work with re-provisioned hosts (E.g. from beaker)
by Barak Korren (oVirt JIRA) 07 Feb '18

07 Feb '18

This is a multi-part message in MIME format... ------------=_1517995701-29869-301 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Barak Korren created OVIRT-1883: ----------------------------------- Summary: Figure out how to make caches work with re-provisioned hosts (E.g. from beaker) Key: OVIRT-1883 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1883 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Slaves Reporter: Barak Korren Assignee: infra The CI system currently relies on the fact that the Jenkins slaves are stateful, and stores various caches on them. If we move to a mechanism where slaves are provisioned dynamically, we need to consider ho to keep having effective caches. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1517995701-29869-301 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Barak Korren created OVIRT-1883:</h3> <pre> Summary: Figure out how to make caches work with re-provisioned hosts (E.g. from beaker) Key: OVIRT-1883 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1883 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Slaves Reporter: Barak Korren Assignee: infra</pre> <p>The CI system currently relies on the fact that the Jenkins slaves are stateful, and stores various caches on them.</p> <p>If we move to a mechanism where slaves are provisioned dynamically, we need to consider ho to keep having effective caches.</p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1517995701-29869-301--

1 0

[CQ]: 87243, 1 (ovirt-engine-extension-aaa-misc) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Feb '18

07 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87243,1 (ovirt-engine-extension-aaa-misc) failed. However, this change seems not to be the root cause for this failure. Change 83287,1 (ovirt-engine-extension-aaa- misc) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 83287,1 (ovirt-engine- extension-aaa-misc) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87243/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/83287/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/573/

1 0

[JIRA] (OVIRT-1880) Manage bare metals with beaker
by Barak Korren (oVirt JIRA) 07 Feb '18

07 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1880?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1880: -------------------------------- Description: There are multiple reasons why we may want to manage our bare-metal slaves with [beaker|https://beaker-project.org/] * It will allow us to have auto-reprovisioning for them, perhaps even after every job * It will allow us to scale up to multiple jenkins masters while sharing host resources * If may allow us to safely move `global_setup.sh` to be executed before a jobs starts and not by the job itself. There are probably multiple pieces of work to be carried out here, each will be tracked in a different ticket that will be set as a blocker to this ticket. was: There are multiple reasons why we may want to manage our bare-metal slaves with beaker: * It will allow us to have auto-reprovisioning for them, perhaps even after every job * It will allow us to scale up to multiple jenkins masters while sharing host resources * If may allow us to safely move `global_setup.sh` to be executed before a jobs starts and not by the job itself. There are probably multiple pieces of work to be carried out here, each will be tracked in a different ticket that will be set as a blocker to this ticket. > Manage bare metals with beaker > ------------------------------ > > Key: OVIRT-1880 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1880 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Slaves > Reporter: Barak Korren > Assignee: infra > > There are multiple reasons why we may want to manage our bare-metal slaves with [beaker|https://beaker-project.org/] > * It will allow us to have auto-reprovisioning for them, perhaps even after every job > * It will allow us to scale up to multiple jenkins masters while sharing host resources > * If may allow us to safely move `global_setup.sh` to be executed before a jobs starts and not by the job itself. > There are probably multiple pieces of work to be carried out here, each will be tracked in a different ticket that will be set as a blocker to this ticket. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

[JIRA] (OVIRT-1881) Setup (or loan) a beaker instance
by Barak Korren (oVirt JIRA) 07 Feb '18

07 Feb '18

This is a multi-part message in MIME format... ------------=_1517995258-24605-194 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1881?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1881: ----------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Setup (or loan) a beaker instance > --------------------------------- > > Key: OVIRT-1881 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1881 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Slaves > Reporter: Barak Korren > Assignee: Evgheni Dereveanchin > Labels: beaker > > To work with Beaker a beaker manager server is needed, some PXE, DNS and DHCP setup is required as well. > We need to check if we can use someone else's beaker server, and if not, setup our own. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1517995258-24605-194 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1881?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren reassigned OVIRT-1881:</h3> <pre>Assignee: Evgheni Dereveanchin (was: infra)</pre> <blockquote><h3>Setup (or loan) a beaker instance</h3> <pre> Key: OVIRT-1881 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1881 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Slaves Reporter: Barak Korren Assignee: Evgheni Dereveanchin Labels: beaker</pre> <p>To work with Beaker a beaker manager server is needed, some PXE, DNS and DHCP setup is required as well. We need to check if we can use someone else's beaker server, and if not, setup our own.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1517995258-24605-194--

1 0

[JIRA] (OVIRT-1882) Figure out how to integrate Jenkins with beaker
by Barak Korren (oVirt JIRA) 07 Feb '18

07 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1882?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1882: ----------------------------------- Assignee: Barak Korren (was: infra) > Figure out how to integrate Jenkins with beaker > ----------------------------------------------- > > Key: OVIRT-1882 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1882 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Master > Reporter: Barak Korren > Assignee: Barak Korren > Labels: beaker > > If we want to use beaker to manage bare-metal slaves, we need a way to connect them to Jenkins. > One way is to run the swarm client on them, and pre-allocate the slaves in beaker, but this would negate the benefit of having beaker re-provision the slaves between job runs. > It would be best if beaker could be configured as a cloud provider in Jenkins so that hosts will be provisioned dynamically as needed. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

[JIRA] (OVIRT-1882) Figure out how to integrate Jenkins with beaker
by Barak Korren (oVirt JIRA) 07 Feb '18

07 Feb '18

This is a multi-part message in MIME format... ------------=_1517995238-13653-236 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Barak Korren created OVIRT-1882: ----------------------------------- Summary: Figure out how to integrate Jenkins with beaker Key: OVIRT-1882 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1882 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Master Reporter: Barak Korren Assignee: infra If we want to use beaker to manage bare-metal slaves, we need a way to connect them to Jenkins. One way is to run the swarm client on them, and pre-allocate the slaves in beaker, but this would negate the benefit of having beaker re-provision the slaves between job runs. It would be best if beaker could be configured as a cloud provider in Jenkins so that hosts will be provisioned dynamically as needed. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1517995238-13653-236 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Barak Korren created OVIRT-1882:</h3> <pre> Summary: Figure out how to integrate Jenkins with beaker Key: OVIRT-1882 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1882 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Master Reporter: Barak Korren Assignee: infra</pre> <p>If we want to use beaker to manage bare-metal slaves, we need a way to connect them to Jenkins.</p> <p>One way is to run the swarm client on them, and pre-allocate the slaves in beaker, but this would negate the benefit of having beaker re-provision the slaves between job runs.</p> <p>It would be best if beaker could be configured as a cloud provider in Jenkins so that hosts will be provisioned dynamically as needed.</p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1517995238-13653-236--

1 0

[JIRA] (OVIRT-1882) Figure out how to integrate Jenkins with beaker
by Barak Korren (oVirt JIRA) 07 Feb '18

07 Feb '18

This is a multi-part message in MIME format... ------------=_1517995238-31531-315 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1882?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1882: -------------------------------- Epic Link: OVIRT-400 > Figure out how to integrate Jenkins with beaker > ----------------------------------------------- > > Key: OVIRT-1882 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1882 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Master > Reporter: Barak Korren > Assignee: infra > Labels: beaker > > If we want to use beaker to manage bare-metal slaves, we need a way to connect them to Jenkins. > One way is to run the swarm client on them, and pre-allocate the slaves in beaker, but this would negate the benefit of having beaker re-provision the slaves between job runs. > It would be best if beaker could be configured as a cloud provider in Jenkins so that hosts will be provisioned dynamically as needed. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1517995238-31531-315 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1882?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1882:</h3> <pre>Epic Link: OVIRT-400</pre> <blockquote><h3>Figure out how to integrate Jenkins with beaker</h3> <pre> Key: OVIRT-1882 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1882 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Master Reporter: Barak Korren Assignee: infra Labels: beaker</pre> <p>If we want to use beaker to manage bare-metal slaves, we need a way to connect them to Jenkins. One way is to run the swarm client on them, and pre-allocate the slaves in beaker, but this would negate the benefit of having beaker re-provision the slaves between job runs. It would be best if beaker could be configured as a cloud provider in Jenkins so that hosts will be provisioned dynamically as needed.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1517995238-31531-315--

1 0

[JIRA] (OVIRT-1881) Setup (or loan) a beaker instance
by Barak Korren (oVirt JIRA) 07 Feb '18

07 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1881?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1881: -------------------------------- Epic Link: OVIRT-403 > Setup (or loan) a beaker instance > --------------------------------- > > Key: OVIRT-1881 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1881 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Slaves > Reporter: Barak Korren > Assignee: infra > Labels: beaker > > To work with Beaker a beaker manager server is needed, some PXE, DNS and DHCP setup is required as well. > We need to check if we can use someone else's beaker server, and if not, setup our own. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

[JIRA] (OVIRT-1881) Setup (or loan) a beaker instance
by Barak Korren (oVirt JIRA) 07 Feb '18

07 Feb '18

Barak Korren created OVIRT-1881: ----------------------------------- Summary: Setup (or loan) a beaker instance Key: OVIRT-1881 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1881 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Slaves Reporter: Barak Korren Assignee: infra To work with Beaker a beaker manager server is needed, some PXE, DNS and DHCP setup is required as well. We need to check if we can use someone else's beaker server, and if not, setup our own. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

[JIRA] (OVIRT-1880) Manage bare metals with beaker
by Barak Korren (oVirt JIRA) 07 Feb '18

07 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1880?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1880: -------------------------------- Description: There are multiple reasons why we may want to manage our bare-metal slaves with beaker: * It will allow us to have auto-reprovisioning for them, perhaps even after every job * It will allow us to scale up to multiple jenkins masters while sharing host resources * If may allow us to safely move `global_setup.sh` to be executed before a jobs starts and not by the job itself. There are probably multiple pieces of work to be carried out here, each will be tracked in a different ticket that will be set as a blocker to this ticket. was: There are multiple reasons why we may want to manage our bare-metal slaves with beaker: * It will allow us to have auto-reprovisioning for them, perhaps even after every job * It will allow us to scale up to multiple jenkins masters while sharing host resources * If may allow us to safely move `global_setup.sh` to be executed before a jobs starts and not by the job itself. > Manage bare metals with beaker > ------------------------------ > > Key: OVIRT-1880 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1880 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Slaves > Reporter: Barak Korren > Assignee: infra > > There are multiple reasons why we may want to manage our bare-metal slaves with beaker: > * It will allow us to have auto-reprovisioning for them, perhaps even after every job > * It will allow us to scale up to multiple jenkins masters while sharing host resources > * If may allow us to safely move `global_setup.sh` to be executed before a jobs starts and not by the job itself. > There are probably multiple pieces of work to be carried out here, each will be tracked in a different ticket that will be set as a blocker to this ticket. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

[JIRA] (OVIRT-1880) Manage bare metals with beaker
by Barak Korren (oVirt JIRA) 07 Feb '18

07 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1880?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1880: -------------------------------- Epic Link: OVIRT-403 > Manage bare metals with beaker > ------------------------------ > > Key: OVIRT-1880 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1880 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Slaves > Reporter: Barak Korren > Assignee: infra > > There are multiple reasons why we may want to manage our bare-metal slaves with beaker: > * It will allow us to have auto-reprovisioning for them, perhaps even after every job > * It will allow us to scale up to multiple jenkins masters while sharing host resources > * If may allow us to safely move `global_setup.sh` to be executed before a jobs starts and not by the job itself. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

[JIRA] (OVIRT-1880) Manage bare metals with beaker
by Barak Korren (oVirt JIRA) 07 Feb '18

07 Feb '18

This is a multi-part message in MIME format... ------------=_1517994329-10691-188 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Barak Korren created OVIRT-1880: ----------------------------------- Summary: Manage bare metals with beaker Key: OVIRT-1880 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1880 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Slaves Reporter: Barak Korren Assignee: infra There are multiple reasons why we may want to manage our bare-metal slaves with beaker: * It will allow us to have auto-reprovisioning for them, perhaps even after every job * It will allow us to scale up to multiple jenkins masters while sharing host resources * If may allow us to safely move `global_setup.sh` to be executed before a jobs starts and not by the job itself. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1517994329-10691-188 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Barak Korren created OVIRT-1880:</h3> <pre> Summary: Manage bare metals with beaker Key: OVIRT-1880 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1880 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Slaves Reporter: Barak Korren Assignee: infra</pre> <p>There are multiple reasons why we may want to manage our bare-metal slaves with beaker:</p> <ul><li><p>It will allow us to have auto-reprovisioning for them, perhaps even after every job</p></li> <li><p>It will allow us to scale up to multiple jenkins masters while sharing host resources</p></li> <li><p>If may allow us to safely move `global_setup.sh` to be executed before a jobs starts and not by the job itself.</p></li></ul> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1517994329-10691-188--

1 0

[CQ]: 87240, 1 (ovirt-hosted-engine-setup) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Feb '18

07 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87240,1 (ovirt-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 86910,1 (ovirt-hosted-engine-setup) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86910,1 (ovirt-hosted-engine- setup) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87240/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86910/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/571/

1 0

[CQ]: 87233, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Feb '18

07 Feb '18

A system test invoked by the "ovirt-master" change queue including change 87233,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87116,5 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87116,5 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87233/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87116/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5312/

1 0

[JIRA] (OVIRT-1879) Rerun-Hooks: all not working anymore
by eyal edri (oVirt JIRA) 07 Feb '18

07 Feb '18

This is a multi-part message in MIME format... ------------=_1517991299-17702-165 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1879?page=com.atlassian.jira.… ] eyal edri reassigned OVIRT-1879: -------------------------------- Assignee: Anton Marchukov (was: infra) > Rerun-Hooks: all not working anymore > ------------------------------------ > > Key: OVIRT-1879 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1879 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: Anton Marchukov > > "Rerun-Hooks: all" is not working anymore. example > https://gerrit.ovirt.org/#/c/79849/ > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1517991299-17702-165 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1879?page=com.atlassian.jira.… ]</pre> <h3>eyal edri reassigned OVIRT-1879:</h3> <pre>Assignee: Anton Marchukov (was: infra)</pre> <blockquote><h3>Rerun-Hooks: all not working anymore</h3> <pre> Key: OVIRT-1879 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1879 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: Anton Marchukov</pre> <p>“Rerun-Hooks: all” is not working anymore. example <a href="https://gerrit.ovirt.org/#/c/79849/">https://gerrit.ovirt.org/#/c/79849/</a> — SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <<a href="https://www.redhat.com/">https://www.redhat.com/</a>> <<a href="https://red.ht/sig">https://red.ht/sig</a>> TRIED. TESTED. TRUSTED. <<a href="https://redhat.com/trusted">https://redhat.com/trusted</a>></p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1517991299-17702-165--

1 0

[CQ]: 86521, 1 (ovirt-engine-sdk-ruby) failed "ovirt-4.2" system tests
by oVirt Jenkins 07 Feb '18

07 Feb '18

Change 86521,1 (ovirt-engine-sdk-ruby) is probably the reason behind recent system test failures in the "ovirt-4.2" 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: https://gerrit.ovirt.org/#/c/86521/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/569/

1 0

Re: [OST][HC] HE fails to deploy
by Sahina Bose 07 Feb '18

07 Feb '18

On Mon, Feb 5, 2018 at 2:59 PM, Sahina Bose <sabose(a)redhat.com> wrote: > Hi all, > > I see the HE fails to deploy after task in running ansible playbook create_target_vm : > > TASK [Wait for the engine to come up on the target VM]", > > with Error engine state=EngineUnexpectedlyDown > > Is this a known issue that you are working on? > > This does seem like a race, because I see that the HC suite again failed with the same error after a successful run yesterday. Do I need to open a bug or do we have one tracking this already? > thanks! > > sahina > > > Full HE setup log at http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_… > >

2 2

[CQ]: 87149, 9 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Feb '18

07 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87149,9 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87027,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87027,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87149/9 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87027/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/567/

1 0

[CQ]: 87148, 9 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Feb '18

07 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87148,9 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87027,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87027,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87148/9 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87027/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/566/

1 0

[CQ]: 87147, 7 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Feb '18

07 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87147,7 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87027,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87027,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87147/7 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87027/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/564/

1 0

[CQ]: 87128, 8 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Feb '18

06 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87128,8 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87027,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87027,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87128/8 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87027/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/562/

1 0

[CQ]: 87131, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Feb '18

06 Feb '18

A system test invoked by the "ovirt-master" change queue including change 87131,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87116,5 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87116,5 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87131/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87116/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5310/

1 0

[CQ]: 87215, 2 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Feb '18

06 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87215,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87027,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87027,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87215/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87027/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/559/

1 0

[CQ]: 87181,2 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 06 Feb '18

06 Feb '18

Change 87181,2 (vdsm) is probably the reason behind recent system test failures in the "ovirt-master" 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: https://gerrit.ovirt.org/#/c/87181/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5309/

1 0

[CQ]: 87116,5 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 06 Feb '18

06 Feb '18

Change 87116,5 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-master" 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: https://gerrit.ovirt.org/#/c/87116/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5307/

1 0

[CQ]: 87146, 5 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Feb '18

06 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87146,5 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87027,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87027,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87146/5 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87027/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/556/

1 0

[CQ]: 87145, 5 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Feb '18

06 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87145,5 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87027,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87027,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87145/5 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87027/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/553/

1 0

[JIRA] (OVIRT-1879) Rerun-Hooks: all not working anymore
by sbonazzo (oVirt JIRA) 06 Feb '18

06 Feb '18

sbonazzo created OVIRT-1879: ------------------------------- Summary: Rerun-Hooks: all not working anymore Key: OVIRT-1879 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1879 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra "Rerun-Hooks: all" is not working anymore. example https://gerrit.ovirt.org/#/c/79849/ -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

[CQ]: 87144, 4 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Feb '18

06 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87144,4 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87027,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87027,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87144/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87027/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/550/

1 0

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #1250
by jenkins＠jenkins.phx.ovirt.org 06 Feb '18

06 Feb '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> Changes: [Barak Korren] Make CQ mark Jenkins URLS in extra_sources [Sandro Bonazzola] ovirt-engine-extension-aaa-ldap: re-align [Ondra Machacek] ovirt-engine-api-metamodel: Mapp 4.2 version to master branch [Ondra Machacek] ovirt-engine-sdk-java: Mapp 4.2 version to master branch [Ondra Machacek] ovirt-engine-sdk-ruby: Mapp 4.2 version to master branch [Ondra Machacek] ovirt-engine-sdk-python: Mapp 4.2 version to master branch [Sandro Bonazzola] ovirt-engine-api-metamodel: drop 4.0 jobs [Sandro Bonazzola] ovirt-engine-sdk-java: re-align [Daniel Belenky] Introduce runners API for stdci [Sandro Bonazzola] ovirt-engine: branched 4.2 [Sandro Bonazzola] ovirt-engine-sdk-ruby: re-align [Tom�� Golembiovsk��] ovirt-guest-agent: prepare for ovirt-4.2 stable branch ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision c203baeb8538005b27cc6bb8a076a8a5f44a7c56 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f c203baeb8538005b27cc6bb8a076a8a5f44a7c56 Commit message: "ovirt-guest-agent: prepare for ovirt-4.2 stable branch" > git rev-list 48b24b30e75fb67d5f72f0e20b38f845ab75b612 # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins148254365122714695.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-updates-el7 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1465, in _commonLoadRepoXML local = self.cachedir + '/repomd.xml' File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda> cachedir = property(lambda self: self._dirGetAttr('cachedir')) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr self.dirSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup self._dirSetupMkdir_p(dir) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p raise Errors.RepoError, msg yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-updates-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-el7' Build step 'Execute shell' marked build as failure

1 1

[CQ]: 87143, 4 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Feb '18

06 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87143,4 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87027,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87027,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87143/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87027/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/546/

1 0

[CQ]: 87142, 4 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Feb '18

06 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87142,4 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87027,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87027,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87142/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87027/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/542/

1 0

[CQ]: 87216, 1 (ovirt-engine-extension-aaa-jdbc) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Feb '18

06 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87216,1 (ovirt-engine-extension-aaa-jdbc) failed. However, this change seems not to be the root cause for this failure. Change 83282,1 (ovirt-engine-extension-aaa- jdbc) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 83282,1 (ovirt-engine- extension-aaa-jdbc) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87216/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/83282/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/538/

1 0

[CQ]: 87214, 2 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Feb '18

06 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87214,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87027,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87027,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87214/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87027/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/535/

1 0

[CQ]: 82230,6 (mom) failed "ovirt-4.2" system tests
by oVirt Jenkins 06 Feb '18

06 Feb '18

Change 82230,6 (mom) is probably the reason behind recent system test failures in the "ovirt-4.2" 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: https://gerrit.ovirt.org/#/c/82230/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/533/

1 0

[CQ]: 87162, 2 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Feb '18

06 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87162,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87027,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87027,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87162/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87027/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/532/

1 0

[CQ]: 87186, 1 (ovirt-engine-extension-logger-log4j) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Feb '18

06 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87186,1 (ovirt-engine-extension-logger-log4j) failed. However, this change seems not to be the root cause for this failure. Change 83288,1 (ovirt-engine-extension- logger-log4j) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 83288,1 (ovirt-engine- extension-logger-log4j) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87186/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/83288/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/530/

1 0

[oVirt Jenkins] ovirt-appliance_ovirt-4.2_build-artifacts-el7-x86_64 - Build # 25 - Failure!
by jenkins＠jenkins.phx.ovirt.org 06 Feb '18

06 Feb '18

------=_Part_430_1552023397.1517315123106 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.2_build-artifacts-el7-… Build: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.2_build-artifacts-el7-… Build Number: 25 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #25 [Daniel Belenky] Add ipinto(a)redhat.com to whitelist [Sandro Bonazzola] vcredist-x86: move to 4.2 and latest fedora [Sandro Bonazzola] pywin32-py2.7: move to 4.2 and latest fedora [Sandro Bonazzola] python-windows: move to 4.2 and latest fedora [Sandro Bonazzola] py2exe-py2.7: move to 4.2 and latest fedora [Sandro Bonazzola] nsis-simple-service-plugin:: move to 4.2 and latest fedora [Daniel Belenky] Bound vdsm check-merged to el7 hosts only [Barak Korren] Make standard-enqueue support non-ovirt queues [Barak Korren] Allow customizing CQ mail addresses [Barak Korren] Enable customizing the server we deploy tested to [Barak Korren] Make pipeline-loader support upstream sources [Barak Korren] Made clone url for 'jenkins' customizable [Sandro Bonazzola] copy-create-job: drop EOLed Fedoras [Dafna Ron] otopi - dropping fc24 [Dafna Ron] ovirt-hosted-engine-setup - dropping fc24 [Daniel Belenky] Mock runner to search full script path [Sandro Bonazzola] otopi: 4.2 and latest fedora [Sandro Bonazzola] ovirt-hosted-engine-setup: 4.2 and new Fedoras [Sandro Bonazzola] ovirt-live: drop project [Daniel Belenky] Introduce Gerrit pipelines [Martin Perina] ovirt-engine-extensions: Add 4.2 jobs for all engine extensions [Yuval Turgeman] Resolve network issues in kickstart ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_430_1552023397.1517315123106--

1 1

[JIRA] (OVIRT-1818) ioprocess build fail on ppc64le
by Barak Korren (oVirt JIRA) 06 Feb '18

06 Feb '18

This is a multi-part message in MIME format... ------------=_1517921995-20639-174 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1818?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1818: -------------------------------- Resolution: Won't Fix Status: Done (was: To Do) > ioprocess build fail on ppc64le > ------------------------------- > > Key: OVIRT-1818 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1818 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: mock_runner > Reporter: Nir Soffer > Assignee: Barak Korren > Labels: ppc64le, standard-ci > > The new builds for ppc64le fail with the errors below. > 1. > http://jenkins.ovirt.org/job/ioprocess_master_check-patch-fc26-ppc64le/1/co… > *00:00:42.499* ERROR: Command failed: *00:00:42.500* # /usr/bin/yum > --installroot /var/lib/mock/fedora-26-ppc64le-881f89337ffa51754418efa2ad261881-16706/root/ > --releasever 26 install @buildsys-build autoconf automake git > glib2-devel python-pip python-six python-subprocess32 python2-devel > python3-devel python3-six util-linux yajl-devel > --setopt=tsflags=nocontexts*00:00:42.500* Failed to set locale, > defaulting to C*00:00:42.500* No package git available.*00:00:42.501* > No package glib2-devel available.*00:00:42.501* No package > python-subprocess32 available.*00:00:42.501* No package python2-devel > available.*00:00:42.501* No package python3-devel > available.*00:00:42.501* No package util-linux > available.*00:00:42.501* No package yajl-devel available. > 2. > http://jenkins.ovirt.org/job/ioprocess_master_check-patch-fc27-ppc64le/1/co… > *00:00:18.335* + > /home/jenkins/workspace/ioprocess_master_check-patch-fc27-ppc64le/jenkins/mock_configs/mock_runner.sh > --patch-only --mock-confs-dir > /home/jenkins/workspace/ioprocess_master_check-patch-fc27-ppc64le/jenkins/mock_configs > --secrets-file /home/jenkins/workspace/ioprocess_master_check-patch-fc27-ppc64le/std_ci_secrets.yaml > --try-proxy --try-mirrors > http://mirrors.phx.ovirt.org/repos/yum/all_latest.json > 'fc27.*ppc64le'*00:00:18.347* Unable to find mock env > fc27.*ppc64le*00:00:18.351* Collecting mock logs*00:00:18.352* mv: > missing destination file operand after 'exported-artifacts/mock_logs' > 3. > http://jenkins.ovirt.org/job/ioprocess_master_check-patch-fcraw-ppc64le/1/c… > *00:00:26.701* + > /home/jenkins/workspace/ioprocess_master_check-patch-fcraw-ppc64le/jenkins/mock_configs/mock_runner.sh > --patch-only --mock-confs-dir > /home/jenkins/workspace/ioprocess_master_check-patch-fcraw-ppc64le/jenkins/mock_configs > --secrets-file /home/jenkins/workspace/ioprocess_master_check-patch-fcraw-ppc64le/std_ci_secrets.yaml > --try-proxy --try-mirrors > http://mirrors.phx.ovirt.org/repos/yum/all_latest.json > 'fcraw.*ppc64le'*00:00:26.702* Unable to find mock env > fcraw.*ppc64le*00:00:26.703* Collecting mock logs > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1517921995-20639-174 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1818?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1818:</h3> <pre>Resolution: Won't Fix Status: Done (was: To Do)</pre> <blockquote><h3>ioprocess build fail on ppc64le</h3> <pre> Key: OVIRT-1818 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1818 Project: oVirt - virtualization made easy Issue Type: Bug Components: mock_runner Reporter: Nir Soffer Assignee: Barak Korren Labels: ppc64le, standard-ci</pre> <p>The new builds for ppc64le fail with the errors below. 1. <a href="http://jenkins.ovirt.org/job/ioprocess_master_check-patch-fc26-ppc64le/1/co…">http://jenkins.ovirt.org/job/ioprocess_master_check-patch-fc26-ppc64le/1/co…</a> <strong>00:00:42.499</strong> ERROR: Command failed: <strong>00:00:42.500</strong> # /usr/bin/yum --installroot /var/lib/mock/fedora-26-ppc64le-881f89337ffa51754418efa2ad261881-16706/root/ --releasever 26 install @buildsys-build autoconf automake git glib2-devel python-pip python-six python-subprocess32 python2-devel python3-devel python3-six util-linux yajl-devel --setopt=tsflags=nocontexts*00:00:42.500* Failed to set locale, defaulting to C*00:00:42.500* No package git available.*00:00:42.501* No package glib2-devel available.*00:00:42.501* No package python-subprocess32 available.*00:00:42.501* No package python2-devel available.*00:00:42.501* No package python3-devel available.*00:00:42.501* No package util-linux available.*00:00:42.501* No package yajl-devel available. 2. <a href="http://jenkins.ovirt.org/job/ioprocess_master_check-patch-fc27-ppc64le/1/co…">http://jenkins.ovirt.org/job/ioprocess_master_check-patch-fc27-ppc64le/1/co…</a> <strong>00:00:18.335</strong> + /home/jenkins/workspace/ioprocess_master_check-patch-fc27-ppc64le/jenkins/mock_configs/mock_runner.sh --patch-only --mock-confs-dir /home/jenkins/workspace/ioprocess_master_check-patch-fc27-ppc64le/jenkins/mock_configs --secrets-file /home/jenkins/workspace/ioprocess_master_check-patch-fc27-ppc64le/std_ci_secrets.yaml --try-proxy --try-mirrors <a href="http://mirrors.phx.ovirt.org/repos/yum/all_latest.json">http://mirrors.phx.ovirt.org/repos/yum/all_latest.json</a> ‘fc27.*ppc64le'*00:00:18.347* Unable to find mock env fc27.*ppc64le*00:00:18.351* Collecting mock logs*00:00:18.352* mv: missing destination file operand after 'exported-artifacts/mock_logs’ 3. <a href="http://jenkins.ovirt.org/job/ioprocess_master_check-patch-fcraw-ppc64le/1/c…">http://jenkins.ovirt.org/job/ioprocess_master_check-patch-fcraw-ppc64le/1/c…</a> <strong>00:00:26.701</strong> + /home/jenkins/workspace/ioprocess_master_check-patch-fcraw-ppc64le/jenkins/mock_configs/mock_runner.sh --patch-only --mock-confs-dir /home/jenkins/workspace/ioprocess_master_check-patch-fcraw-ppc64le/jenkins/mock_configs --secrets-file /home/jenkins/workspace/ioprocess_master_check-patch-fcraw-ppc64le/std_ci_secrets.yaml --try-proxy --try-mirrors <a href="http://mirrors.phx.ovirt.org/repos/yum/all_latest.json">http://mirrors.phx.ovirt.org/repos/yum/all_latest.json</a> 'fcraw.*ppc64le'*00:00:26.702* Unable to find mock env fcraw.*ppc64le*00:00:26.703* Collecting mock logs Nir</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1517921995-20639-174--

1 0

[JIRA] (OVIRT-1878) GitHub support for pusher.py
by Barak Korren (oVirt JIRA) 06 Feb '18

06 Feb '18

This is a multi-part message in MIME format... ------------=_1517920058-25756-160 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1878?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1878: -------------------------------- Epic Link: OVIRT-400 > GitHub support for pusher.py > ---------------------------- > > Key: OVIRT-1878 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1878 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: pusher.py > Reporter: Barak Korren > Assignee: infra > Labels: github > > '{{pusher.py}}' currently only supports gerrit, what this means in practice is that automated polling for upstream source changes is only available for repos that are hosted in Gerrit. > We need to support this in GitHub as well. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1517920058-25756-160 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1878?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1878:</h3> <pre>Epic Link: OVIRT-400</pre> <blockquote><h3>GitHub support for pusher.py</h3> <pre> Key: OVIRT-1878 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1878 Project: oVirt - virtualization made easy Issue Type: Improvement Components: pusher.py Reporter: Barak Korren Assignee: infra Labels: github</pre> <p>‘{{pusher.py}}’ currently only supports gerrit, what this means in practice is that automated polling for upstream source changes is only available for repos that are hosted in Gerrit. We need to support this in GitHub as well.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1517920058-25756-160--

1 0

[JIRA] (OVIRT-1878) GitHub support for pusher.py
by Barak Korren (oVirt JIRA) 06 Feb '18

06 Feb '18

Barak Korren created OVIRT-1878: ----------------------------------- Summary: GitHub support for pusher.py Key: OVIRT-1878 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1878 Project: oVirt - virtualization made easy Issue Type: Improvement Components: pusher.py Reporter: Barak Korren Assignee: infra '{{pusher.py}}' currently only supports gerrit, what this means in practice is that automated polling for upstream source changes is only available for repos that are hosted in Gerrit. We need to support this in GitHub as well. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

[JIRA] (OVIRT-1877) Update docs to indicated adding 'jenkins:' prefix to build URLs
by eyal edri (oVirt JIRA) 06 Feb '18

06 Feb '18

This is a multi-part message in MIME format... ------------=_1517918909-19670-172 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1877?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1877: ---------------------------------- [~gbenhaim(a)redhat.com] [~sbonazolla(a)redhat.com] [~amarchuk] FYI. > Update docs to indicated adding 'jenkins:' prefix to build URLs > --------------------------------------------------------------- > > Key: OVIRT-1877 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1877 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Documentation > Reporter: Barak Korren > Assignee: infra > > Our infra includes multipile places where users can input text that is used as configuration for repoman. Users are typically expected to place URLs of build jobs there to make repoman acquire built artifacts (For e.g. testing). > So far documentation specified that the plain URL to the build job can be used. This turns out to only be true for builds made on jenkins.ovirt.org. For URLs pointing at other jenkins servers, the '{{jenkins:}}' prefix needs to be added. > Documentation should be updated to teach users to add the '{{jenkins:}}' prefix. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1517918909-19670-172 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1877?page=com.atlassian.jira.… ]</pre> <h3>eyal edri commented on OVIRT-1877:</h3> <p>[~gbenhaim(a)redhat.com] [~sbonazolla(a)redhat.com] [~amarchuk] FYI.</p> <blockquote><h3>Update docs to indicated adding ‘jenkins:’ prefix to build URLs</h3> <pre> Key: OVIRT-1877 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1877 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Documentation Reporter: Barak Korren Assignee: infra</pre> <p>Our infra includes multipile places where users can input text that is used as configuration for repoman. Users are typically expected to place URLs of build jobs there to make repoman acquire built artifacts (For e.g. testing). So far documentation specified that the plain URL to the build job can be used. This turns out to only be true for builds made on jenkins.ovirt.org. For URLs pointing at other jenkins servers, the ‘{{jenkins:}}’ prefix needs to be added. Documentation should be updated to teach users to add the ‘{{jenkins:}}’ prefix.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1517918909-19670-172--

1 0

[CQ]: 87140, 3 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Feb '18

06 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87140,3 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87027,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87027,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87140/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87027/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/521/

3 2

[CQ]: 87072, 1 (ovirt-guest-agent) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Feb '18

06 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87072,1 (ovirt-guest-agent) failed. However, this change seems not to be the root cause for this failure. Change 83813,1 (ovirt-guest-agent) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 83813,1 (ovirt-guest-agent) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87072/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/83813/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/528/

1 0

[CQ]: 83288, 1 (ovirt-engine-extension-logger-log4j) failed "ovirt-4.2" system tests
by oVirt Jenkins 06 Feb '18

06 Feb '18

Change 83288,1 (ovirt-engine-extension-logger-log4j) is probably the reason behind recent system test failures in the "ovirt-4.2" 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: https://gerrit.ovirt.org/#/c/83288/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/527/

1 0

[JIRA] (OVIRT-1877) Update docs to indicated adding 'jenkins:' prefix to build URLs
by eyal edri (oVirt JIRA) 06 Feb '18

06 Feb '18

This is a multi-part message in MIME format... ------------=_1517911412-28556-136 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1877?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1877: ---------------------------------- Adding potential locations to update: * OST docs * Manual job * repoman docs * Official oVirt releases > Update docs to indicated adding 'jenkins:' prefix to build URLs > --------------------------------------------------------------- > > Key: OVIRT-1877 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1877 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Documentation > Reporter: Barak Korren > Assignee: infra > > Our infra includes multipile places where users can input text that is used as configuration for repoman. Users are typically expected to place URLs of build jobs there to make repoman acquire built artifacts (For e.g. testing). > So far documentation specified that the plain URL to the build job can be used. This turns out to only be true for builds made on jenkins.ovirt.org. For URLs pointing at other jenkins servers, the '{{jenkins:}}' prefix needs to be added. > Documentation should be updated to teach users to add the '{{jenkins:}}' prefix. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1517911412-28556-136 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1877?page=com.atlassian.jira.… ]</pre> <h3>eyal edri commented on OVIRT-1877:</h3> <p>Adding potential locations to update:</p> <ul><li><p>OST docs</p></li> <li><p>Manual job</p></li> <li><p>repoman docs</p></li> <li><p>Official oVirt releases</p></li></ul> <blockquote><h3>Update docs to indicated adding ‘jenkins:’ prefix to build URLs</h3> <pre> Key: OVIRT-1877 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1877 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Documentation Reporter: Barak Korren Assignee: infra</pre> <p>Our infra includes multipile places where users can input text that is used as configuration for repoman. Users are typically expected to place URLs of build jobs there to make repoman acquire built artifacts (For e.g. testing). So far documentation specified that the plain URL to the build job can be used. This turns out to only be true for builds made on jenkins.ovirt.org. For URLs pointing at other jenkins servers, the ‘{{jenkins:}}’ prefix needs to be added. Documentation should be updated to teach users to add the ‘{{jenkins:}}’ prefix.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1517911412-28556-136--

1 0

[JIRA] (OVIRT-1877) Update docs to indicated adding 'jenkins:' prefix to build URLs
by Barak Korren (oVirt JIRA) 06 Feb '18

06 Feb '18

This is a multi-part message in MIME format... ------------=_1517911157-10812-203 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Barak Korren created OVIRT-1877: ----------------------------------- Summary: Update docs to indicated adding 'jenkins:' prefix to build URLs Key: OVIRT-1877 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1877 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Documentation Reporter: Barak Korren Assignee: infra Our infra includes multipile places where users can input text that is used as configuration for repoman. Users are typically expected to place URLs of build jobs there to make repoman acquire built artifacts (For e.g. testing). So far documentation specified that the plain URL to the build job can be used. This turns out to only be true for builds made on jenkins.ovirt.org. For URLs pointing at other jenkins servers, the '{{jenkins:}}' prefix needs to be added. Documentation should be updated to teach users to add the '{{jenkins:}}' prefix. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1517911157-10812-203 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Barak Korren created OVIRT-1877:</h3> <pre> Summary: Update docs to indicated adding 'jenkins:' prefix to build URLs Key: OVIRT-1877 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1877 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Documentation Reporter: Barak Korren Assignee: infra</pre> <p>Our infra includes multipile places where users can input text that is used as configuration for repoman. Users are typically expected to place URLs of build jobs there to make repoman acquire built artifacts (For e.g. testing).</p> <p>So far documentation specified that the plain URL to the build job can be used. This turns out to only be true for builds made on jenkins.ovirt.org. For URLs pointing at other jenkins servers, the ‘{{jenkins:}}’ prefix needs to be added.</p> <p>Documentation should be updated to teach users to add the ‘{{jenkins:}}’ prefix.</p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1517911157-10812-203--

1 0

[JIRA] (OVIRT-1877) Update docs to indicated adding 'jenkins:' prefix to build URLs
by Barak Korren (oVirt JIRA) 06 Feb '18

06 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1877?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1877: -------------------------------- Epic Link: OVIRT-400 > Update docs to indicated adding 'jenkins:' prefix to build URLs > --------------------------------------------------------------- > > Key: OVIRT-1877 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1877 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Documentation > Reporter: Barak Korren > Assignee: infra > > Our infra includes multipile places where users can input text that is used as configuration for repoman. Users are typically expected to place URLs of build jobs there to make repoman acquire built artifacts (For e.g. testing). > So far documentation specified that the plain URL to the build job can be used. This turns out to only be true for builds made on jenkins.ovirt.org. For URLs pointing at other jenkins servers, the '{{jenkins:}}' prefix needs to be added. > Documentation should be updated to teach users to add the '{{jenkins:}}' prefix. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

[CQ]: 87186, 1 (ovirt-engine-extension-logger-log4j) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Feb '18

06 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87186,1 (ovirt-engine-extension-logger-log4j) failed. However, this change seems not to be the root cause for this failure. Change 83288,1 (ovirt-engine-extension- logger-log4j) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 83288,1 (ovirt-engine- extension-logger-log4j) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87186/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/83288/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/525/

1 0

[CQ]: 83288, 1 (ovirt-engine-extension-logger-log4j) failed "ovirt-4.2" system tests
by oVirt Jenkins 06 Feb '18

06 Feb '18

Change 83288,1 (ovirt-engine-extension-logger-log4j) is probably the reason behind recent system test failures in the "ovirt-4.2" 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: https://gerrit.ovirt.org/#/c/83288/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/523/

1 0

Re: [oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 183 - Failure!
by Eyal Edri 06 Feb '18

06 Feb '18

On Feb 6, 2018 10:37, "Simone Tiraboschi" <stirabos(a)redhat.com> wrote: On Tue, Feb 6, 2018 at 9:15 AM, Sandro Bonazzola <sbonazzo(a)redhat.com> wrote: > I see: > > *04:29:42* Error: Ansible(>= 2.2) is not installed.*04:29:42* Some of the features might not work if not installed. > > > Followed by: > > *04:29:53* Running test scenario 002_bootstrap.py*04:29:53* + env_run_test /home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-master/ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py*04:29:53* + local res=0*04:29:53* + cd /home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-master/ovirt-system-tests/deployment-hc-basic-suite-master*04:29:53* + lago ovirt runtest /home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-master/ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py*04:29:53* @ Run test: 002_bootstrap.py: *04:29:53* nose.config: INFO: Ignoring files matching ['^\\.', '^_', '^setup\\.py$']*04:29:53* # wait_engine: *04:42:13* * Collect artifacts: *04:42:30* - [Thread-4] lago-hc-basic-suite-master-engine: ERROR (in 0:00:16)*04:42:30* Error while running thread*04:42:30* Traceback (most recent call last):*04:42:30* File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue*04:42:30* queue.put({'return': func()})*04:42:30* File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1504, in _collect_artifacts*04:42:30* vm.collect_artifacts(path, ignore_nopath)*04:42:30* File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line 635, in collect_artifacts*04:42:30* ignore_nopath=ignore_nopath*04:42:30* File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line 381, in extract_paths*04:42:30* return self.provider.extract_paths(paths, *args, **kwargs)*04:42:30* File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line 251, in extract_paths*04:42:30* format(self.vm.name())*04:42:30* ExtractPathError: Unable to extract paths from lago-hc-basic-suite-master-engine: unreachable with SSH > > > lago is not able to extract logs from the engine because the engine vm is down. > > The deploy failed with: > > > 2018-02-05 22:29:38,221-0500 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:190 ansible-playbook stderr: > 2018-02-05 22:29:38,222-0500 DEBUG otopi.context context._executeMethod:143 method exception > Traceback (most recent call last): > File "/usr/lib/python2.7/site-packages/otopi/context.py", line 133, in _executeMethod > method['method']() > File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-ansiblesetup/core/target_vm.py", line 193, in _closeup > r = ah.run() > File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/ansible_utils.py", line 194, in run > raise RuntimeError(_('Failed executing ansible-playbook')) > RuntimeError: Failed executing ansible-playbook > > Didi, Simone, can you please have a look? > > The issue is here: Feb 5 22:21:39 lago-hc-basic-suite-master-host0 libvirtd: 2018-02-06 03:21:39.367+0000: 16907: error : x86ModelFromCPU:1061 : internal error: Unknown CPU model Haswell-noTSXIBRS We are incorrectly handling the CPU model name for AMD and IBRS enabled families. We have an open bug here: https://bugzilla.redhat.com/show_bug.cgi?id=1541328 We fixed a similar issue for basic suite, it might fail on slave with outdated lago-ost-plugin. Gal, can you please have a look to see if it's the same issue we fixed already? > Ansible logs are at: > > http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/183/a… > > > > > > > > > > > > 2018-02-06 4:43 GMT+01:00 <jenkins(a)jenkins.phx.ovirt.org>: > >> Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-sui >> te-master/ >> Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-sui >> te-master/183/ >> Build Number: 183 >> Build Status: Failure >> Triggered By: Started by timer >> >> ------------------------------------- >> Changes Since Last Success: >> ------------------------------------- >> Changes for Build #183 >> [Sandro Bonazzola] hc-basic-suite-4.1: add centos-qemu-ev-release-el7 >> >> [Sandro Bonazzola] ovirt-engine: dropped fcraw on master >> >> [Barak Korren] Add a timeout to pipline STDCI jobs >> >> [Sandro Bonazzola] ovirt-guest-agent: drop el6 on >= 4.2 >> >> >> >> >> ----------------- >> Failed Tests: >> ----------------- >> No tests ran. >> _______________________________________________ >> Infra mailing list >> Infra(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/infra >> >> > > > -- > > SANDRO BONAZZOLA > > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D > > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > > _______________________________________________ Infra mailing list Infra(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

2 1

[CQ]: 85992,1 (ovirt-wgt) failed "ovirt-master" system tests
by oVirt Jenkins 06 Feb '18

06 Feb '18

Change 85992,1 (ovirt-wgt) is probably the reason behind recent system test failures in the "ovirt-master" 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: https://gerrit.ovirt.org/#/c/85992/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5287/

2 1

[oVirt Jenkins] ovirt-system-tests_he-basic-suite-master - Build # 190 - Failure!
by jenkins＠jenkins.phx.ovirt.org 06 Feb '18

06 Feb '18

------=_Part_16_556802572.1517540299963 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/190/ Build Number: 190 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #190 [Yaniv Kaul] Move add_vm1_from_template test to APIv4 [Dafna Ron] ovirt-host-deploy - dropping fc24 [Sandro Bonazzola] ovirt-host-deploy: re-align [Dafna Ron] ovirt-engine-wildfly - dropping fc24 [Sandro Bonazzola] ovirt-engine-wildfly: re-align [Evgheni Dereveanchin] Update mirror snapshot for FC27 to fix gdbm [Dafna Ron] ovirt-engine-wildfly-overlay - dropping fc24 [Sandro Bonazzola] ovirt-engine-wildfly-overlay: re-align [Gal Ben Haim] kubevirt-ansible: Update org [Sandro Bonazzola] ovirt-setup-lib: branched for 4.3 development [Sandro Bonazzola] ovirt-guest-agent: re-align [Nir Soffer] ioprocess: Add project for 4.2 [Martin Sivak] Cleanup and prepare SLA packages for 4.2 [Dafna Ron] ovirt-engine-nodejs - dropping fc24 [Sandro Bonazzola] ovirt-engine-nodejs: re-align [Dafna Ron] ovirt-image-uploader - dropping fc24 [Sandro Bonazzola] ovirt-image-uploader: re-align [Yuval Turgeman] ovirt-appliance: set node-filter to el7 [Barak Korren] Fix CQ exceptions on removed jobs [Barak Korren] Make change-queue-tester not wait for deployment [Barak Korren] Limit projects that standard-enqueue triggers on [Daniel Belenky] dsl: Fixed a bug in pipeline dict formatter [Dafna Ron] ovirt-engine-nodejs-modules - dropping fc24 [Sandro Bonazzola] ovirt-engine-nodejs-modules: re-align [Yedidyah Bar David] Add 4.2 jobs for ovirt-engine [Dafna Ron] ovirt-engine-extension-logger-log4j - dropping fc24 [Dafna Ron] ovirt-engine-yarn - dropping fc24 [Sandro Bonazzola] ovirt-engine-extension-logger-log4j: re-align [Sandro Bonazzola] ovirt-engine-yarn: re-align [Dafna Ron] ovirt-vmconsole - dropping fc24 [Sandro Bonazzola] ovirt-vmconsole: re-align ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_16_556802572.1517540299963--

1 5

[oVirt Jenkins] ovirt-system-tests_he-basic-ansible-suite-master - Build # 23 - Failure!
by jenkins＠jenkins.phx.ovirt.org 06 Feb '18

06 Feb '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-mast… Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-mast… Build Number: 23 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #23 [Yaniv Kaul] Move add_vm1_from_template test to APIv4 [Barak Korren] Fix CQ exceptions on removed jobs [Barak Korren] Make change-queue-tester not wait for deployment [Barak Korren] Limit projects that standard-enqueue triggers on [Daniel Belenky] dsl: Fixed a bug in pipeline dict formatter [Dafna Ron] ovirt-engine-nodejs-modules - dropping fc24 [Sandro Bonazzola] ovirt-engine-nodejs-modules: re-align [Yedidyah Bar David] Add 4.2 jobs for ovirt-engine [Dafna Ron] ovirt-engine-extension-logger-log4j - dropping fc24 [Dafna Ron] ovirt-engine-yarn - dropping fc24 [Sandro Bonazzola] ovirt-engine-extension-logger-log4j: re-align [Sandro Bonazzola] ovirt-engine-yarn: re-align [Dafna Ron] ovirt-vmconsole - dropping fc24 [Sandro Bonazzola] ovirt-vmconsole: re-align ----------------- Failed Tests: ----------------- No tests ran.

2 7

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.1 - Build # 166 - Failure!
by jenkins＠jenkins.phx.ovirt.org 05 Feb '18

05 Feb '18

------=_Part_381_1544163873.1517107231092 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.1/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.1/166/ Build Number: 166 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #166 [Dan Kenigsberg] networking: vm_operations: use a vm with a vnic ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_381_1544163873.1517107231092--

3 12

[CQ]: 85992,1 (ovirt-wgt) failed "ovirt-master" system tests
by oVirt Jenkins 05 Feb '18

05 Feb '18

Change 85992,1 (ovirt-wgt) is probably the reason behind recent system test failures in the "ovirt-master" 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: https://gerrit.ovirt.org/#/c/85992/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5285/

1 0

[CQ]: 86896,2 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 05 Feb '18

05 Feb '18

Change 86896,2 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-master" 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: https://gerrit.ovirt.org/#/c/86896/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5283/

1 0

[CQ]: 87109, 6 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Feb '18

05 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87109,6 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87027,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87027,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87109/6 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87027/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/519/

1 0

[CQ]: 86896, 2 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Feb '18

05 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 86896,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87027,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87027,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/86896/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87027/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/518/

1 0

[CQ]: 86927, 2 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Feb '18

05 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 86927,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87027,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87027,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/86927/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87027/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/516/

1 0

[CQ]: 85380, 5 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Feb '18

05 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 85380,5 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87027,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87027,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/85380/5 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87027/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/514/

1 0

[CQ]: 87158, 3 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Feb '18

05 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87158,3 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87027,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87027,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87158/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87027/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/511/

1 0

[CQ]: 86974, 2 (ovirt-engine-dashboard) failed "ovirt-master" system tests
by oVirt Jenkins 05 Feb '18

05 Feb '18

Change 86974,2 (ovirt-engine-dashboard) is probably the reason behind recent system test failures in the "ovirt-master" 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: https://gerrit.ovirt.org/#/c/86974/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5280/

1 0

[CQ]: 86884, 5 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Feb '18

05 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 86884,5 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87027,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87027,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/86884/5 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87027/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/508/

1 0

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #1244
by jenkins＠jenkins.phx.ovirt.org 05 Feb '18

05 Feb '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 1a50d6d60ddb901eb280ba70895fdbe2f8063306 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 1a50d6d60ddb901eb280ba70895fdbe2f8063306 Commit message: "dsl: Search for different ci configurations" > git rev-list 1a50d6d60ddb901eb280ba70895fdbe2f8063306 # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins3219906071628485055.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-updates-el7 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1465, in _commonLoadRepoXML local = self.cachedir + '/repomd.xml' File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda> cachedir = property(lambda self: self._dirGetAttr('cachedir')) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr self.dirSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup self._dirSetupMkdir_p(dir) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p raise Errors.RepoError, msg yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-updates-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-el7' Build step 'Execute shell' marked build as failure

2 2

[CQ]: 87134, 1 (ovirt-engine-nodejs-modules) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Feb '18

05 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87134,1 (ovirt-engine-nodejs-modules) failed. However, this change seems not to be the root cause for this failure. Change 86512,2 (ovirt-engine-nodejs-modules) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86512,2 (ovirt-engine-nodejs- modules) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87134/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86512/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/506/

2 1

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 159 - Failure!
by jenkins＠jenkins.phx.ovirt.org 05 Feb '18

05 Feb '18

------=_Part_113_1228656558.1516074596162 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/159/ Build Number: 159 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #159 [Gal Ben Haim] 4.2: Adding 4.2 pre repo ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.add_hosts Error Message: Host lago-hc-basic-suite-master-host1 failed to install -------------------- >> begin captured logging << -------------------- ovirtlago.testlib: ERROR: * Unhandled exception in <function _host_is_up at 0x3d80668> Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 219, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-master/ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", line 151, in _host_is_up raise RuntimeError('Host %s failed to install' % host.name()) RuntimeError: Host lago-hc-basic-suite-master-host1 failed to install --------------------- >> end captured logging << --------------------- Stack Trace: File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 129, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-master/ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", line 164, in add_hosts testlib.assert_true_within(_host_is_up, timeout=15 * 60) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 263, in assert_true_within assert_equals_within(func, True, timeout, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 219, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-master/ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", line 151, in _host_is_up raise RuntimeError('Host %s failed to install' % host.name()) 'Host lago-hc-basic-suite-master-host1 failed to install\n-------------------- >> begin captured logging << --------------------\novirtlago.testlib: ERROR: * Unhandled exception in <function _host_is_up at 0x3d80668>\nTraceback (most recent call last):\n File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 219, in assert_equals_within\n res = func()\n File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-master/ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", line 151, in _host_is_up\n raise RuntimeError(\'Host %s failed to install\' % host.name())\nRuntimeError: Host lago-hc-basic-suite-master-host1 failed to install\n--------------------- >> end captured logging << ---------------------' ------=_Part_113_1228656558.1516074596162--

1 23

[CQ]: 87156, 1 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Feb '18

05 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87156,1 (cockpit-ovirt) failed. However, this change seems not to be the root cause for this failure. Change 86648,1 (cockpit-ovirt) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86648,1 (cockpit-ovirt) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87156/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86648/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/504/

1 0

fcraw Jenkins build fails on import error
by Tal Nisan 05 Feb '18

05 Feb '18

*http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-fcraw-x86_64/29/consoleFull <http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-fcraw-x86_64/2…>* *10:53:31* ==================================== ERRORS ====================================*10:53:31* ERROR collecting packaging/setup/tests/ovirt_engine_setup/engine_common/test_database.py *10:53:31* ImportError while importing test module '/home/jenkins/workspace/ovirt-engine_master_check-patch-fcraw-x86_64/ovirt-engine/packaging/setup/tests/ovirt_engine_setup/engine_common/test_database.py'.*10:53:31* Hint: make sure your test modules/packages have valid Python names.*10:53:31* Traceback:*10:53:31* packaging/setup/tests/ovirt_engine_setup/engine_common/test_database.py:19: in <module>*10:53:31* import ovirt_engine_setup.engine_common.database as under_test # isort:skip # noqa: E402*10:53:31* packaging/setup/ovirt_engine_setup/engine_common/database.py:30: in <module>*10:53:31* from otopi import base*10:53:31* E ImportError: No module named otopi*10:53:31* !!!!!!!!!!!!!!!!!!! Interrupted: 1 errors during collection !!!!!!!!!!!!!!!!!!!!*10:53:31* =========================== 1 error in 0.43 seconds ============================

4 5

[CQ]: 87141, 2 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Feb '18

05 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87141,2 (cockpit-ovirt) failed. However, this change seems not to be the root cause for this failure. Change 86648,1 (cockpit-ovirt) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86648,1 (cockpit-ovirt) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87141/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86648/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/503/

1 0

[CQ]: 87092, 2 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Feb '18

05 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87092,2 (cockpit-ovirt) failed. However, this change seems not to be the root cause for this failure. Change 86648,1 (cockpit-ovirt) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86648,1 (cockpit-ovirt) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87092/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86648/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/501/

1 0

he-basic suite fails due to ioprocess mismatch
by Yedidyah Bar David 05 Feb '18

05 Feb '18

Hi all, Tried it now and it still fails [1] with the same error: 10:32:30 Error: Package: python-ioprocess-1.0.0-1.201711301358.git33b51a0.el7.centos.noarch (alocalsync) 10:32:30 Requires: ioprocess = 1.0.0 10:32:30 Available: ioprocess-1.0.2-1.201802041151.gitb3db88d.el7.centos.x86_64 (alocalsync) 10:32:30 ioprocess = 1.0.2-1.201802041151.gitb3db88d.el7.centos No idea where 'python-ioprocess-1.0.0-1.201711301358.git33b51a0.el7.centos.noarch' comes from. Might be a bad repo somewhere or a bug in reposync. Is anyone handling this? Thanks, [1] http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-mast… -- Didi

2 2

[CQ]: 87115, 2 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Feb '18

05 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87115,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87027,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87027,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87115/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87027/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/499/

1 0

[JIRA] (OVIRT-1523) Support multipile executors per CI stage (V2)
by Barak Korren (oVirt JIRA) 05 Feb '18

05 Feb '18

This is a multi-part message in MIME format... ------------=_1517821033-24001-150 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1523?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1523: ----------------------------------- Assignee: Daniel Belenky (was: infra) > Support multipile executors per CI stage (V2) > --------------------------------------------- > > Key: OVIRT-1523 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1523 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: Daniel Belenky > Labels: standard-ci > > Currently we allow creating just one Jenkins "Free-Style" job per standard-CI stage and distribution. This means for e.g. that you can only have one "check-patch" script running on EL7 for a given project. > It had been requested several times to allow having multiple standard-CI scripts running in parallel on separate slaves as a means to get CI results faster. > Implementing this properly will probably require implementing both OVIRT-1522 and OVIRT-1013 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1517821033-24001-150 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1523?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren reassigned OVIRT-1523:</h3> <pre>Assignee: Daniel Belenky (was: infra)</pre> <blockquote><h3>Support multipile executors per CI stage (V2)</h3> <pre> Key: OVIRT-1523 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1523 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: Daniel Belenky Labels: standard-ci</pre> <p>Currently we allow creating just one Jenkins “Free-Style” job per standard-CI stage and distribution. This means for e.g. that you can only have one “check-patch” script running on EL7 for a given project. It had been requested several times to allow having multiple standard-CI scripts running in parallel on separate slaves as a means to get CI results faster. Implementing this properly will probably require implementing both OVIRT-1522 and OVIRT-1013</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1517821033-24001-150--

1 0

[JIRA] (OVIRT-1523) Support multipile executors per CI stage (V2)
by Barak Korren (oVirt JIRA) 05 Feb '18

05 Feb '18

This is a multi-part message in MIME format... ------------=_1517820996-15267-159 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1523?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1523: ------------------------------------- The work on OVIRT-1875 would provide solution to this ticket as the DSL already include a built-in "sub-stages" feature. > Support multipile executors per CI stage (V2) > --------------------------------------------- > > Key: OVIRT-1523 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1523 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > Currently we allow creating just one Jenkins "Free-Style" job per standard-CI stage and distribution. This means for e.g. that you can only have one "check-patch" script running on EL7 for a given project. > It had been requested several times to allow having multiple standard-CI scripts running in parallel on separate slaves as a means to get CI results faster. > Implementing this properly will probably require implementing both OVIRT-1522 and OVIRT-1013 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1517820996-15267-159 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1523?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren commented on OVIRT-1523:</h3> <p>The work on OVIRT-1875 would provide solution to this ticket as the DSL already include a built-in “sub-stages” feature.</p> <blockquote><h3>Support multipile executors per CI stage (V2)</h3> <pre> Key: OVIRT-1523 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1523 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra Labels: standard-ci</pre> <p>Currently we allow creating just one Jenkins “Free-Style” job per standard-CI stage and distribution. This means for e.g. that you can only have one “check-patch” script running on EL7 for a given project. It had been requested several times to allow having multiple standard-CI scripts running in parallel on separate slaves as a means to get CI results faster. Implementing this properly will probably require implementing both OVIRT-1522 and OVIRT-1013</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1517820996-15267-159--

1 0

[JIRA] (OVIRT-1876) Make it possible to create poll-upstream-sources jobs from STDCI pipelines/DSL
by Barak Korren (oVirt JIRA) 05 Feb '18

05 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1876?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1876: -------------------------------- Epic Link: OVIRT-400 > Make it possible to create poll-upstream-sources jobs from STDCI pipelines/DSL > ------------------------------------------------------------------------------ > > Key: OVIRT-1876 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1876 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: pusher.py, Standard CI (Pipelines), STDCI DSL, usrc.py > Reporter: Barak Korren > Assignee: infra > > The `poll-upstream-sources` jobs are the last kind of STDCI job that do not yet have pipeline-based implementation. > This has not been done so far because pipelines typically once in the project lifetime and then run in response to user SCM events. The poll job OTOH may need to be created and removed in response to user changes to the STDCI DSL. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

[JIRA] (OVIRT-1876) Make it possible to create poll-upstream-sources jobs from STDCI pipelines/DSL
by Barak Korren (oVirt JIRA) 05 Feb '18

05 Feb '18

Barak Korren created OVIRT-1876: ----------------------------------- Summary: Make it possible to create poll-upstream-sources jobs from STDCI pipelines/DSL Key: OVIRT-1876 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1876 Project: oVirt - virtualization made easy Issue Type: Improvement Components: pusher.py, Standard CI (Pipelines), STDCI DSL, usrc.py Reporter: Barak Korren Assignee: infra The `poll-upstream-sources` jobs are the last kind of STDCI job that do not yet have pipeline-based implementation. This has not been done so far because pipelines typically once in the project lifetime and then run in response to user SCM events. The poll job OTOH may need to be created and removed in response to user changes to the STDCI DSL. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

[JIRA] (OVIRT-1690) Add CI for groovy/pipeline code in 'jenkins' repo
by Barak Korren (oVirt JIRA) 05 Feb '18

05 Feb '18

This is a multi-part message in MIME format... ------------=_1517820316-20903-134 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1690?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1690: -------------------------------- Labels: first_time_task groovy jenkins (was: groovy jenkins) > Add CI for groovy/pipeline code in 'jenkins' repo > ------------------------------------------------- > > Key: OVIRT-1690 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1690 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: CI client projects > Reporter: Barak Korren > Assignee: infra > Labels: first_time_task, groovy, jenkins > > We don't have any CI for Groovy code currently. > At the very least we need to check that the code compiles, this is a bit harder then it sounds because in order to test compilation for piepline code we need to mock out things like the '{{NonCPS}}' decorator which is not supported by the standard Groovy compiler. > Ideally we can also ass support for a full test suit. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1517820316-20903-134 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1690?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1690:</h3> <pre>Labels: first_time_task groovy jenkins (was: groovy jenkins)</pre> <blockquote><h3>Add CI for groovy/pipeline code in ‘jenkins’ repo</h3> <pre> Key: OVIRT-1690 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1690 Project: oVirt - virtualization made easy Issue Type: Improvement Components: CI client projects Reporter: Barak Korren Assignee: infra Labels: first_time_task, groovy, jenkins</pre> <p>We don't have any CI for Groovy code currently. At the very least we need to check that the code compiles, this is a bit harder then it sounds because in order to test compilation for piepline code we need to mock out things like the ‘{{NonCPS}}’ decorator which is not supported by the standard Groovy compiler. Ideally we can also ass support for a full test suit.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1517820316-20903-134--

1 0

[JIRA] (OVIRT-1875) Integrate new DSL syntax with STDCI pipelines
by Barak Korren (oVirt JIRA) 05 Feb '18

05 Feb '18

This is a multi-part message in MIME format... ------------=_1517819933-13572-142 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1875?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1875: ----------------------------------- Assignee: Daniel Belenky (was: infra) > Integrate new DSL syntax with STDCI pipelines > --------------------------------------------- > > Key: OVIRT-1875 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1875 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Standard CI (Pipelines), STDCI DSL > Reporter: Barak Korren > Assignee: Daniel Belenky > > Work on core code for the STDCI DSL is not mostly done, its time for the next phase of integrating it with the existing STDCI pipeline code to start using it in production. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1517819933-13572-142 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1875?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren reassigned OVIRT-1875:</h3> <pre>Assignee: Daniel Belenky (was: infra)</pre> <blockquote><h3>Integrate new DSL syntax with STDCI pipelines</h3> <pre> Key: OVIRT-1875 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1875 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Standard CI (Pipelines), STDCI DSL Reporter: Barak Korren Assignee: Daniel Belenky</pre> <p>Work on core code for the STDCI DSL is not mostly done, its time for the next phase of integrating it with the existing STDCI pipeline code to start using it in production.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1517819933-13572-142--

1 0

[JIRA] (OVIRT-1875) Integrate new DSL syntax with STDCI pipelines
by Barak Korren (oVirt JIRA) 05 Feb '18

05 Feb '18

This is a multi-part message in MIME format... ------------=_1517819918-16546-132 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Barak Korren created OVIRT-1875: ----------------------------------- Summary: Integrate new DSL syntax with STDCI pipelines Key: OVIRT-1875 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1875 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Standard CI (Pipelines), STDCI DSL Reporter: Barak Korren Assignee: infra Work on core code for the STDCI DSL is not mostly done, its time for the next phase of integrating it with the existing STDCI pipeline code to start using it in production. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1517819918-16546-132 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Barak Korren created OVIRT-1875:</h3> <pre> Summary: Integrate new DSL syntax with STDCI pipelines Key: OVIRT-1875 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1875 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Standard CI (Pipelines), STDCI DSL Reporter: Barak Korren Assignee: infra</pre> <p>Work on core code for the STDCI DSL is not mostly done, its time for the next phase of integrating it with the existing STDCI pipeline code to start using it in production.</p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1517819918-16546-132--

1 0

[JIRA] (OVIRT-1875) Integrate new DSL syntax with STDCI pipelines
by Barak Korren (oVirt JIRA) 05 Feb '18

05 Feb '18

This is a multi-part message in MIME format... ------------=_1517819918-10866-119 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1875?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1875: -------------------------------- Epic Link: OVIRT-400 > Integrate new DSL syntax with STDCI pipelines > --------------------------------------------- > > Key: OVIRT-1875 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1875 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Standard CI (Pipelines), STDCI DSL > Reporter: Barak Korren > Assignee: infra > > Work on core code for the STDCI DSL is not mostly done, its time for the next phase of integrating it with the existing STDCI pipeline code to start using it in production. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1517819918-10866-119 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1875?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1875:</h3> <pre>Epic Link: OVIRT-400</pre> <blockquote><h3>Integrate new DSL syntax with STDCI pipelines</h3> <pre> Key: OVIRT-1875 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1875 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Standard CI (Pipelines), STDCI DSL Reporter: Barak Korren Assignee: infra</pre> <p>Work on core code for the STDCI DSL is not mostly done, its time for the next phase of integrating it with the existing STDCI pipeline code to start using it in production.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1517819918-10866-119--

1 0