[CQ]: 102914, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 102914,3 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 101913,10 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

[CQ]: 102983, 4 (ovirt-engine-nodejs-modules) failed "ovirt-4.2" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-4.2" change queue including change 102983,4 (ovirt-engine-nodejs-modules) failed. However, this change seems not to be the root cause for this failure. Change 102923,3 (ovirt-engine-nodejs-modules) that this change depends on or is based on, was detected as the

[CQ]: 102983, 4 (ovirt-engine-nodejs-modules) failed "ovirt-4.3" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-4.3" change queue including change 102983,4 (ovirt-engine-nodejs-modules) failed. However, this change seems not to be the root cause for this failure. Change 102982,4 (ovirt-engine-nodejs-modules) that this change depends on or is based on, was detected as the

[CQ]: 102982, 4 (ovirt-engine-nodejs-modules) failed "ovirt-4.2" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-4.2" change queue including change 102982,4 (ovirt-engine-nodejs-modules) failed. However, this change seems not to be the root cause for this failure. Change 102923,3 (ovirt-engine-nodejs-modules) that this change depends on or is based on, was detected as the

[CQ]: 102982, 4 (ovirt-engine-nodejs-modules) failed "ovirt-4.3" system tests

Change 102982,4 (ovirt-engine-nodejs-modules) is probably the reason behind recent system test failures in the "ovirt-4.3" 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

Build failed in Jenkins: system-sync_mirrors-sac-gluster-ansible-el7-x86_64 #131

See -- Started by timer Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in

[oVirt Jenkins] ovirt-system-tests_compat-4.3-suite-master - Build # 182 - Failure!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.3-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.3-suite-master/182/ Build Number: 182 Build Status: Failure Triggered By: Started by timer - Changes Since Last

[CQ]: 103029, 2 (ovirt-provider-ovn) failed "ovirt-master" system tests

Change 103029,2 (ovirt-provider-ovn) 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

[CQ]: 66bcd08 (ovirt-web-ui) failed "ovirt-master" system tests

Change 66bcd08 (ovirt-web-ui) 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

[CQ]: 102840, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 102840,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 101913,10 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

[CQ]: 102492, 6 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 102492,6 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 101913,10 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

oVirt infra daily report - unstable production jobs - 936

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/936//artifact/exported-artifacts/upstream_report.html Cheers, Jenkins

[CQ]: 102229, 11 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 102229,11 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 101913,10 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

[CQ]: 103019, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 103019,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 101913,10 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

[CQ]: 102981, 2 (ovirt-engine-nodejs-modules) failed "ovirt-master" system tests

Change 102981,2 (ovirt-engine-nodejs-modules) 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

[CQ]: 102939, 7 (ovirt-host-deploy) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 102939,7 (ovirt-host-deploy) failed. However, this change seems not to be the root cause for this failure. Change 102372,4 (ovirt-host-deploy) that this change depends on or is based on, was detected as the cause of the

[CQ]: 102838, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 102838,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 101913,10 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

Build failed in Jenkins: system-sync_mirrors-sac-gluster-ansible-el7-x86_64 #130

See -- Started by timer Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in

[CQ]: 102235,24 (vdsm) failed "ovirt-master" system tests

Change 102235,24 (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

[CQ]: 66bcd08 (ovirt-web-ui) failed "ovirt-4.2" system tests

Change 66bcd08 (ovirt-web-ui) 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

[CQ]: 102348, 8 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 102348,8 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 101913,10 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

[JIRA] (OVIRT-2787) connecting to ci slave as developer account

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39776#comment-39776 ] Eyal Edri commented on OVIRT-2787: -- I’m not sure it's possible with the current implementation of Jenkins in

[JIRA] (OVIRT-2787) connecting to ci slave as developer account

Or Shoval created OVIRT-2787: Summary: connecting to ci slave as developer account Key: OVIRT-2787 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2787 Project: oVirt - virtualization made easy

[CQ]: 102981, 2 (ovirt-engine-nodejs-modules) failed "ovirt-4.2" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-4.2" change queue including change 102981,2 (ovirt-engine-nodejs-modules) failed. However, this change seems not to be the root cause for this failure. Change 102923,3 (ovirt-engine-nodejs-modules) that this change depends on or is based on, was detected as the

[JIRA] (OVIRT-2764) send email on changequeue-status_master_standard-poll-upstream-sources failure

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ehud Yonasi reassigned OVIRT-2764: -- Assignee: Ehud Yonasi (was: infra) > send email on

Re: URGENT - ovirt-engine master is failing for the past 9 days

Done On Mon, Sep 2, 2019 at 2:46 PM Dafna Ron wrote: > Thanks Andrej, > Tal, can you merge? > > Thanks, > Dafna > > > On Mon, Sep 2, 2019 at 2:42 PM Andrej Krejcir wrote: > >> This patch fixes the issue: https://gerrit.ovirt.org/#/c/103019/ >> >> On Mon, 2 Sep 2019 at 10:16, Andrej Krejcir

Re: URGENT - ovirt-engine master is failing for the past 9 days

Thanks Andrej, Tal, can you merge? Thanks, Dafna On Mon, Sep 2, 2019 at 2:42 PM Andrej Krejcir wrote: > This patch fixes the issue: https://gerrit.ovirt.org/#/c/103019/ > > On Mon, 2 Sep 2019 at 10:16, Andrej Krejcir wrote: > >> I will post a fix later today. Sorry for the delay, It took me

[JIRA] (OVIRT-2764) send email on changequeue-status_master_standard-poll-upstream-sources failure

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39774#comment-39774 ] Eyal Edri commented on OVIRT-2764: -- [~accountid:5aa0f39f5a4d022884128a0f] can you verify this is done? >

Re: URGENT - ovirt-engine master is failing for the past 9 days

This patch fixes the issue: https://gerrit.ovirt.org/#/c/103019/ On Mon, 2 Sep 2019 at 10:16, Andrej Krejcir wrote: > I will post a fix later today. Sorry for the delay, It took me a while to > figure out what is the problem. > > On Sun, 1 Sep 2019 at 14:58, Tal Nisan wrote: > >> OST failing

[JIRA] (OVIRT-2782) Configure Jenkins to wait less and allocate more

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eyal Edri reassigned OVIRT-2782: Assignee: Evgheni Dereveanchin (was: infra) > Configure Jenkins to wait less and allocate more

Build failed in Jenkins: system-sync_mirrors-sac-gluster-ansible-el7-x86_64 #129

See Changes: [Barak Korren] gate: Filter releases by change queue prefix -- Started by timer Running as SYSTEM [EnvInject] - Loading node

[CQ]: 103009, 1 (ovirt-host) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 103009,1 (ovirt-host) failed. However, this change seems not to be the root cause for this failure. Change 101396,1 (ovirt-host) that this change depends on or is based on, was detected as the cause of the testing failures.

[CQ]: 103006, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 103006,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 101913,10 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

Re: URGENT - ovirt-engine master is failing for the past 9 days

I will post a fix later today. Sorry for the delay, It took me a while to figure out what is the problem. On Sun, 1 Sep 2019 at 14:58, Tal Nisan wrote: > OST failing for 9 days is totally unacceptable, the only reason I'm not > sending a revert patch is that it'll make a bloody mess with the

[JIRA] (OVIRT-2786) Re: fc30 packages in master snapshot

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39769#comment-39769 ] Dafna Ron commented on OVIRT-2786: -- I am surprised it did not comment on the bug as it usually does and it

Re: [JIRA] (OVIRT-2786) Re: fc30 packages in master snapshot

I am surprised it did not comment on the bug as it usually does and it also sends a mail to the list. However, I think as we are going to work with zuul, it may not be effective to work on CQ :) On Mon, Sep 2, 2019 at 10:52 AM Yedidyah Bar David wrote: > On Mon, Sep 2, 2019 at 10:47 AM Dafna

Re: [JIRA] (OVIRT-2786) Re: fc30 packages in master snapshot

On Mon, Sep 2, 2019 at 10:47 AM Dafna Ron (oVirt JIRA) wrote: > > > [ > https://ovirt-jira.atlassian.net/browse/OVIRT-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39768#comment-39768 > ] > > Dafna Ron commented on OVIRT-2786: >

[JIRA] (OVIRT-2786) Re: fc30 packages in master snapshot

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39768#comment-39768 ] Dafna Ron commented on OVIRT-2786: -- packages only get into tested once they pass CQ. I looked at the latest

[JIRA] (OVIRT-2786) Re: fc30 packages in master snapshot

Anton Marchukov created OVIRT-2786: -- Summary: Re: fc30 packages in master snapshot Key: OVIRT-2786 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2786 Project: oVirt - virtualization made easy

fc30 packages in master snapshot

Hi, How are these published? A few days ago we merged patches to add fc30 builds of otopi and ovirt-host-deploy. Jenkins ran build-artifacts on them and all seems good. But we do not see them in [1]. Should we? Are they stuck somewhere, or there is simply nothing that publishes them these days?

Re: Removing big (hc-* and metrics) suits from OST's check-patch (How to make OST faster in CI)

Adding Evgeny and Shirly who are AFAIK the owners of the metrics suit. On Sun, 1 Sep 2019 at 17:07, Barak Korren wrote: > If you have been using or monitoring any OST suits recently, you may have > noticed we've been suffering from long delays in allocating CI hardware > resources for running