February 2018 - Infra - oVirt List Archives

[CQ]: 34cc3c3 (ovirt-ansible-image-template) failed "ovirt-4.2" system tests
by oVirt Jenkins 12 Feb '18

12 Feb '18

Change 34cc3c3 (ovirt-ansible-image-template) 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://github.com/oVirt/ovirt-ansible-image-template/commit/34cc3c3922b81c… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/713/

1 0

[CQ]: 449099e (ovirt-ansible-repositories) failed "ovirt-4.2" system tests
by oVirt Jenkins 12 Feb '18

12 Feb '18

Change 449099e (ovirt-ansible-repositories) 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://github.com/oVirt/ovirt-ansible-repositories/commit/449099ea80719d43… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/709/

1 0

[JIRA] (OVIRT-1894) Add conditional execution parameter (run_if) to DSL options
by Daniel Belenky (oVirt JIRA) 12 Feb '18

12 Feb '18

This is a multi-part message in MIME format... ------------=_1518448129-17839-165 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1894?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-1894: ------------------------------------- Assignee: Daniel Belenky (was: infra) > Add conditional execution parameter (run_if) to DSL options > ----------------------------------------------------------- > > Key: OVIRT-1894 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1894 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: STDCI DSL > Reporter: Daniel Belenky > Assignee: Daniel Belenky > > We want to have the ability to specify conditional execution of threads (stage, substage, ... ) with different conditions. > The first condition to implement (and probably the most straightforward one) is to execute a thread in certain files were changed. > Example schema for the syntax: > {code:yaml} > --- > stage: check-patch > substage: > - change1: > run-if: > - file-changed: <filename> > - change2: > run-if: > - file-changed: > - <file1> > - <file2> > {code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1518448129-17839-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-1894?page=com.atlassian.jira.… ]</pre> <h3>Daniel Belenky reassigned OVIRT-1894:</h3> <pre>Assignee: Daniel Belenky (was: infra)</pre> <blockquote><h3>Add conditional execution parameter (run_if) to DSL options</h3> <pre> Key: OVIRT-1894 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1894 Project: oVirt - virtualization made easy Issue Type: Improvement Components: STDCI DSL Reporter: Daniel Belenky Assignee: Daniel Belenky</pre> <p>We want to have the ability to specify conditional execution of threads (stage, substage, … ) with different conditions. The first condition to implement (and probably the most straightforward one) is to execute a thread in certain files were changed. Example schema for the syntax: {code:yaml} --- stage: check-patch substage:</p> <pre> - change1: run-if: - file-changed: <filename> - change2: run-if: - file-changed: - <file1> - <file2></pre> <p>{code}</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> ------------=_1518448129-17839-165--

1 0

[JIRA] (OVIRT-1894) Add conditional execution parameter (run_if) to DSL options
by Daniel Belenky (oVirt JIRA) 12 Feb '18

12 Feb '18

This is a multi-part message in MIME format... ------------=_1518448116-12711-117 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1894?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-1894: ---------------------------------- Epic Link: OVIRT-400 > Add conditional execution parameter (run_if) to DSL options > ----------------------------------------------------------- > > Key: OVIRT-1894 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1894 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: STDCI DSL > Reporter: Daniel Belenky > Assignee: infra > > We want to have the ability to specify conditional execution of threads (stage, substage, ... ) with different conditions. > The first condition to implement (and probably the most straightforward one) is to execute a thread in certain files were changed. > Example schema for the syntax: > {code:yaml} > --- > stage: check-patch > substage: > - change1: > run-if: > - file-changed: <filename> > - change2: > run-if: > - file-changed: > - <file1> > - <file2> > {code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1518448116-12711-117 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1894?page=com.atlassian.jira.… ]</pre> <h3>Daniel Belenky updated OVIRT-1894:</h3> <pre>Epic Link: OVIRT-400</pre> <blockquote><h3>Add conditional execution parameter (run_if) to DSL options</h3> <pre> Key: OVIRT-1894 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1894 Project: oVirt - virtualization made easy Issue Type: Improvement Components: STDCI DSL Reporter: Daniel Belenky Assignee: infra</pre> <p>We want to have the ability to specify conditional execution of threads (stage, substage, … ) with different conditions. The first condition to implement (and probably the most straightforward one) is to execute a thread in certain files were changed. Example schema for the syntax: {code:yaml} --- stage: check-patch substage:</p> <pre> - change1: run-if: - file-changed: <filename> - change2: run-if: - file-changed: - <file1> - <file2></pre> <p>{code}</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> ------------=_1518448116-12711-117--

1 0

[JIRA] (OVIRT-1894) Add conditional execution parameter (run_if) to DSL options
by Daniel Belenky (oVirt JIRA) 12 Feb '18

12 Feb '18

Daniel Belenky created OVIRT-1894: ------------------------------------- Summary: Add conditional execution parameter (run_if) to DSL options Key: OVIRT-1894 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1894 Project: oVirt - virtualization made easy Issue Type: Improvement Components: STDCI DSL Reporter: Daniel Belenky Assignee: infra We want to have the ability to specify conditional execution of threads (stage, substage, ... ) with different conditions. The first condition to implement (and probably the most straightforward one) is to execute a thread in certain files were changed. Example schema for the syntax: {code:yaml} --- stage: check-patch substage: - change1: run-if: - file-changed: <filename> - change2: run-if: - file-changed: - <file1> - <file2> {code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

[CQ]: 87396,1 (ovirt-live) failed "ovirt-master" system tests
by oVirt Jenkins 12 Feb '18

12 Feb '18

Change 87396,1 (ovirt-live) 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/87396/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5617/

1 0

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

12 Feb '18

------=_Part_209_1031571882.1518446894793 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/standard-enqueue/9982/ Build Name: #9982 Build Description: Gerrit: 87408 - ovirt-log-collector (3.6) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/87408 - title: automation: add stdci - project: ovirt-log-collector - branch: ovirt-log-collector-3.6 - author: Sandro Bonazzola <sbonazzo(a)redhat.com> ------=_Part_209_1031571882.1518446894793--

1 0

[CQ]: 46998fa (ovirt-ansible-infra) failed "ovirt-4.2" system tests
by oVirt Jenkins 12 Feb '18

12 Feb '18

Change 46998fa (ovirt-ansible-infra) 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://github.com/oVirt/ovirt-ansible-infra/commit/46998fa9f79051ed435cd07… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/705/

1 0

[CQ]: a11d8a2 (ovirt-ansible-cluster-upgrade) failed "ovirt-4.2" system tests
by oVirt Jenkins 12 Feb '18

12 Feb '18

Change a11d8a2 (ovirt-ansible-cluster-upgrade) 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://github.com/oVirt/ovirt-ansible-cluster-upgrade/commit/a11d8a267cc9e… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/702/

1 0

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

12 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87486,4 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 87418,2 (ovirt-provider-ovn) 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 87418,2 (ovirt-provider-ovn) 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/87486/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87418/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/700/

1 0