[CQ]: 83872, 1 (ovirt-engine-api-model) failed "ovirt-master" system tests

2017-11-09 Thread oVirt Jenkins
Change 83872,1 (ovirt-engine-api-model) 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

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.1 - Build # 87 - Failure!

2017-11-09 Thread jenkins
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.1/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.1/87/ Build Number: 87 Build Status: Failure Triggered By: Started by timer - Changes Since Last Success:

Build failed in Jenkins: system-sync_mirrors-centos-extras-el7-x86_64 #894

2017-11-09 Thread jenkins
See -- Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace

Jenkins build became unstable: ovirt_master_publish-rpms_nightly #763

2017-11-09 Thread jenkins
See ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 83644,3 (ovirt-engine) failed "ovirt-master" system tests

2017-11-09 Thread oVirt Jenkins
Change 83644,3 (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

oVirt infra daily report - unstable production jobs - 500

2017-11-09 Thread jenkins
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/500//artifact/exported-artifacts/upstream_report.html Cheers, Jenkins

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

2017-11-09 Thread oVirt Jenkins
A system test invoked by the "ovirt-master" change queue including change 82887,3 (ovirt-vdsmfake) failed. However, this change seems not to be the root cause for this failure. Change 79056,2 (ovirt-vdsmfake) that this change depends on or is based on, was detected as the cause of the testing

[CQ]: 82888, 4 (ovirt-vdsmfake) failed "ovirt-master" system tests, but isn't the failure root cause

2017-11-09 Thread oVirt Jenkins
A system test invoked by the "ovirt-master" change queue including change 82888,4 (ovirt-vdsmfake) failed. However, this change seems not to be the root cause for this failure. Change 79056,2 (ovirt-vdsmfake) that this change depends on or is based on, was detected as the cause of the testing

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

2017-11-09 Thread oVirt Jenkins
A system test invoked by the "ovirt-master" change queue including change 82886,2 (ovirt-vdsmfake) failed. However, this change seems not to be the root cause for this failure. Change 79056,2 (ovirt-vdsmfake) that this change depends on or is based on, was detected as the cause of the testing

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

2017-11-09 Thread oVirt Jenkins
A system test invoked by the "ovirt-master" change queue including change 82884,1 (ovirt-vdsmfake) failed. However, this change seems not to be the root cause for this failure. Change 79056,2 (ovirt-vdsmfake) that this change depends on or is based on, was detected as the cause of the testing

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

2017-11-09 Thread oVirt Jenkins
A system test invoked by the "ovirt-master" change queue including change 82883,1 (ovirt-vdsmfake) failed. However, this change seems not to be the root cause for this failure. Change 79056,2 (ovirt-vdsmfake) that this change depends on or is based on, was detected as the cause of the testing

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

2017-11-09 Thread oVirt Jenkins
A system test invoked by the "ovirt-master" change queue including change 80570,2 (ovirt-vdsmfake) failed. However, this change seems not to be the root cause for this failure. Change 79056,2 (ovirt-vdsmfake) that this change depends on or is based on, was detected as the cause of the testing

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

2017-11-09 Thread oVirt Jenkins
A system test invoked by the "ovirt-master" change queue including change 82882,1 (ovirt-vdsmfake) failed. However, this change seems not to be the root cause for this failure. Change 79056,2 (ovirt-vdsmfake) that this change depends on or is based on, was detected as the cause of the testing

[JIRA] (OVIRT-1750) CI +1 doesn't carry forward on commit message updated while previous build is running

2017-11-09 Thread Greg Sheremeta (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=35315#comment-35315 ] Greg Sheremeta commented on OVIRT-1750: --- Ok, thanks :) > CI +1 doesn't carry forward on commit message

[JIRA] (OVIRT-1750) CI +1 doesn't carry forward on commit message updated while previous build is running

2017-11-09 Thread Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=35314#comment-35314 ] Barak Korren commented on OVIRT-1750: - [~gsher...@redhat.com] this is a race condition, Jenkins is posting

[JIRA] (OVIRT-1750) CI +1 doesn't carry forward on commit message updated while previous build is running

2017-11-09 Thread Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-1750: Resolution: Won't Fix Status: Done (was: To Do) > CI +1 doesn't carry forward on commit

[JIRA] (OVIRT-1750) CI +1 doesn't carry forward on commit message updated while previous build is running

2017-11-09 Thread Greg Sheremeta (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Sheremeta updated OVIRT-1750: -- Attachment: Selection_263.png > CI +1 doesn't carry forward on commit message updated while

[JIRA] (OVIRT-1750) CI +1 doesn't carry forward on commit message updated while previous build is running

2017-11-09 Thread Greg Sheremeta (oVirt JIRA)
Greg Sheremeta created OVIRT-1750: - Summary: CI +1 doesn't carry forward on commit message updated while previous build is running Key: OVIRT-1750 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1750

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

2017-11-09 Thread oVirt Jenkins
Change 83785,1 (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

Build failed in Jenkins: system-sync_mirrors-centos-extras-el7-x86_64 #893

2017-11-09 Thread jenkins
See -- Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.1 ] [ 09-11-2017 ] [ 001_upgrade_engine.test_initialize_engine ]

2017-11-09 Thread Dafna Ron
On 11/09/2017 02:03 PM, Martin Perina wrote: > > > On Thu, Nov 9, 2017 at 2:49 PM, Dafna Ron > wrote: > > Hi, > > We had a failure in installing engine with a dependency error > between ovirt-engine-backend and vdsm-jsonrpc-java > > Please

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

2017-11-09 Thread oVirt Jenkins
Change 83814,2 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details

[JIRA] (OVIRT-1749) Please create new repositories on ovirt github for new Ansible roles

2017-11-09 Thread Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren reassigned OVIRT-1749: --- Assignee: Barak Korren (was: infra) Epic Link: OVIRT-403 > Please create new

[JIRA] (OVIRT-1749) Please create new repositories on ovirt github for new Ansible roles

2017-11-09 Thread Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-1749: Epic Link: OVIRT-403 > Please create new repositories on ovirt github for new Ansible roles >

[oVirt Jenkins] standard-enqueue - Build #6651 - FAILURE!

2017-11-09 Thread jenkins
Build: http://jenkins.ovirt.org/job/standard-enqueue/6651/ Build Name: #6651 Build Description: Gerrit: 83846 - ovirt-scheduler-proxy (3.6, 4.0, 4.1, master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/83846 - title: Do not create home directory for the new user during

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.1 ] [ 09-11-2017 ] [ 001_upgrade_engine.test_initialize_engine ]

2017-11-09 Thread Martin Perina
On Thu, Nov 9, 2017 at 2:49 PM, Dafna Ron wrote: > Hi, > > We had a failure in installing engine with a dependency error between > ovirt-engine-backend and vdsm-jsonrpc-java > > Please note that we have other issues which are not related to this patch > so it might be hard to

Re: [ OST Failure Report ] [ oVirt 4.1 ] [ 09-11-2017 ] [ 001_upgrade_engine.test_initialize_engine ]

2017-11-09 Thread Piotr Kliczewski
On Thu, Nov 9, 2017 at 2:49 PM, Dafna Ron wrote: > Hi, > > We had a failure in installing engine with a dependency error between > ovirt-engine-backend and vdsm-jsonrpc-java > > Please note that we have other issues which are not related to this patch > so it might be hard to

[ OST Failure Report ] [ oVirt 4.1 ] [ 09-11-2017 ] [ 001_upgrade_engine.test_initialize_engine ]

2017-11-09 Thread Dafna Ron
Hi, We had a failure in installing engine with a dependency error between ovirt-engine-backend and vdsm-jsonrpc-java Please note that we have other issues which are not related to this patch so it might be hard to find this issue. I also added the lago log where you can find the package

[CQ]: 81712, 13 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests

2017-11-09 Thread oVirt Jenkins
Change 81712,13 (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

[JIRA] (OVIRT-1748) include ovirt-guest-agent in Fedora and CentOS images provided on glance.ovirt.org

2017-11-09 Thread danken (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=35312#comment-35312 ] danken commented on OVIRT-1748: --- [~sbonazo...@redhat.com], what would it take to include an enabled

Build failed in Jenkins: system-sync_mirrors-centos-extras-el7-x86_64 #892

2017-11-09 Thread jenkins
See Changes: [Martin Perina] ovirt-engine: Add FC26 build -- Started by timer [EnvInject] - Loading node environment variables. Building

[oVirt Jenkins] standard-enqueue - Build #6589 - FAILURE!

2017-11-09 Thread jenkins
Build: http://jenkins.ovirt.org/job/standard-enqueue/6589/ Build Name: #6589 Build Description: Gerrit: 83800 - ovirt-engine (3.6) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/83800 - title: build: post ovirt-engine-3.6.12.2 - project: ovirt-engine - branch: ovirt-engine-3.6 -

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

2017-11-09 Thread oVirt Jenkins
A system test invoked by the "ovirt-4.1" change queue including change 83798,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 82995,4 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures.

[oVirt Jenkins] standard-enqueue - Build #6588 - FAILURE!

2017-11-09 Thread jenkins
Build: http://jenkins.ovirt.org/job/standard-enqueue/6588/ Build Name: #6588 Build Description: Gerrit: 83799 - ovirt-engine (3.6) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/83799 - title: build: ovirt-engine-3.6.12.2 - project: ovirt-engine - branch: ovirt-engine-3.6 - author: