- Infra - oVirt List Archives

[JIRA] (OVIRT-1888) can_sudo function has to accept multiple positional parameters
by Daniel Belenky (oVirt JIRA) 07 Feb '18

07 Feb '18

This is a multi-part message in MIME format... ------------=_1518007951-31730-368 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Daniel Belenky created OVIRT-1888: ------------------------------------- Summary: can_sudo function has to accept multiple positional parameters Key: OVIRT-1888 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1888 Project: oVirt - virtualization made easy Issue Type: Bug Components: oVirt CI Reporter: Daniel Belenky Assignee: infra Currently, can_sudo function in global_setup and slave_cleanup is accepting only one param but in it's calls sometimes we pass more than one param to check for permissions. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1518007951-31730-368 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Daniel Belenky created OVIRT-1888:</h3> <pre> Summary: can_sudo function has to accept multiple positional parameters Key: OVIRT-1888 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1888 Project: oVirt - virtualization made easy Issue Type: Bug Components: oVirt CI Reporter: Daniel Belenky Assignee: infra</pre> <p>Currently, can_sudo function in global_setup and slave_cleanup is accepting only one param but in it's calls sometimes we pass more than one param to check for permissions.</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> ------------=_1518007951-31730-368--

1 0

[JIRA] (OVIRT-1888) can_sudo function has to accept multiple positional parameters
by Daniel Belenky (oVirt JIRA) 07 Feb '18

07 Feb '18

This is a multi-part message in MIME format... ------------=_1518007951-14942-348 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1888?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-1888: ---------------------------------- Epic Link: OVIRT-400 > can_sudo function has to accept multiple positional parameters > -------------------------------------------------------------- > > Key: OVIRT-1888 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1888 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Daniel Belenky > Assignee: infra > > Currently, can_sudo function in global_setup and slave_cleanup is accepting only one param but in it's calls sometimes we pass more than one param to check for permissions. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1518007951-14942-348 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1888?page=com.atlassian.jira.… ]</pre> <h3>Daniel Belenky updated OVIRT-1888:</h3> <pre>Epic Link: OVIRT-400</pre> <blockquote><h3>can_sudo function has to accept multiple positional parameters</h3> <pre> Key: OVIRT-1888 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1888 Project: oVirt - virtualization made easy Issue Type: Bug Components: oVirt CI Reporter: Daniel Belenky Assignee: infra</pre> <p>Currently, can_sudo function in global_setup and slave_cleanup is accepting only one param but in it's calls sometimes we pass more than one param to check for permissions.</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> ------------=_1518007951-14942-348--

1 0

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

07 Feb '18

Change 69504,1 (ovirt-engine-cli) 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/69504/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/580/

1 0

[CQ]: 69504,1 (ovirt-engine-cli) failed "ovirt-4.1" system tests
by oVirt Jenkins 07 Feb '18

07 Feb '18

Change 69504,1 (ovirt-engine-cli) is probably the reason behind recent system test failures in the "ovirt-4.1" 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/69504/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.1_change-queue-tester/1601/

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: ---------------------------------- Epic Link: OVIRT-400 > 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: 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

[ 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