- Infra - oVirt List Archives

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

03 Mar '18

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

1 0

[CQ]: 88137, 5 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 02 Mar '18

02 Mar '18

A system test invoked by the "ovirt-master" change queue including change 88137,5 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 88402,4 (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 88402,4 (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/88137/5 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/88402/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/6025/

1 0

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

02 Mar '18

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

1 0

OST Failure - Weekly update [24/02/2018-02/03/2018]
by Dafna Ron 02 Mar '18

02 Mar '18

Hello, I would like to update on this week's failures and OST current status. We had a failed change that caused other changes to fail: 1. Remove use of end_play and fail module - https://gerrit.ovirt.org/#/c/88250/ date: 27-02-2018 version: master/4.2 test failed: 002_bootstrap.verify_add_hosts fix: reverted until it can be fixed: https://gerrit.ovirt.org/#/c/88327/ bug: https://bugzilla.redhat.com/show_bug.cgi?id=1540260 I re-triggered some of the failed changes that were effected by the above change. However, I am still seeing ovirt-engine project is failing in cq so I am expecting some new issues to appear which would be reported next week. *Below you can see the chart for this week's resolved issues but cause of failure: * Code= regression of working components/functionalities Configurations - package related issues Other = failed build artifacts Infra = infrastructure/OST/Lago related issues <https://gerrit.ovirt.org/#/c/88327/> <https://gerrit.ovirt.org/#/c/88327/> <https://gerrit.ovirt.org/#/c/88327/> *Below is a chart of resolved failures based on ovirt version* *Below is a chart showing failures by suite type: * Thank you, Dafna <https://gerrit.ovirt.org/#/c/88327/>

1 0

[CQ]: 85505, 5 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 02 Mar '18

02 Mar '18

A system test invoked by the "ovirt-master" change queue including change 85505,5 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 88402,4 (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 88402,4 (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/85505/5 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/88402/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/6018/

1 0

[CQ]: 88402,4 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 02 Mar '18

02 Mar '18

Change 88402,4 (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/88402/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/6016/

1 0

[CQ]: 88046, 11 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests
by oVirt Jenkins 02 Mar '18

02 Mar '18

Change 88046,11 (ovirt-hosted-engine-setup) 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/88046/11 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5866/

4 8

[oVirt CI] standard-enqueue - Build #10842 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 02 Mar '18

02 Mar '18

------=_Part_121_1399173834.1520000736197 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/standard-enqueue/10842/ Build Name: #10842 Build Description: Gerrit: 88128 - ovirt-engine-sdk-java (3.6, 4.1, 4.2, master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/88128 - title: Skip javadoc creation on fc28 - project: ovirt-engine-sdk-java - branch: sdk_3.6 - author: Ondra Machacek <omachace(a)redhat.com> ------=_Part_121_1399173834.1520000736197--

1 0

[JIRA] (OST-99) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
by Greg Sheremeta (oVirt JIRA) 02 Mar '18

02 Mar '18

This is a multi-part message in MIME format... ------------=_1519999376-14302-262 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OST-99?page=com.atlassian.jira.plug… ] Greg Sheremeta commented on OST-99: ----------------------------------- > I would not start with the container I'm close to having something pretty nice with docker-compose and the docker API via OST :) > new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium > ------------------------------------------------------------------------------ > > Key: OST-99 > URL: https://ovirt-jira.atlassian.net/browse/OST-99 > Project: oVirt system tests > Issue Type: Improvement > Reporter: Greg Sheremeta > Assignee: infra > > I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. > The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. > Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. > Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) ------------=_1519999376-14302-262 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OST-99?page=com.atlassian.jira.plug… ]</pre> <h3>Greg Sheremeta commented on OST-99:</h3> <blockquote><p>I would not start with the container</p></blockquote> <p>I'm close to having something pretty nice with docker-compose and the docker API via OST :)</p> <blockquote><h3>new ui_sanity scenario for basic_suite — need multiple firefoxes and chromium</h3> <pre> Key: OST-99 URL: https://ovirt-jira.atlassian.net/browse/OST-99 Project: oVirt system tests Issue Type: Improvement Reporter: Greg Sheremeta Assignee: infra</pre> <p>I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.)</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)</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> ------------=_1519999376-14302-262--

1 0

[CQ]: 88365, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 02 Mar '18

02 Mar '18

A system test invoked by the "ovirt-master" change queue including change 88365,3 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87902,10 (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 87902,10 (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/88365/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87902/10 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/6007/

1 0