Jenkins build is back to normal : system-sync_mirrors-centos-updates-el7-x86_64 #1235

2018-02-01 Thread jenkins
See ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] ovirt-appliance_ovirt-4.2-snapshot_build-artifacts-el7-x86_64 - Build # 152 - Fixed!

2018-02-01 Thread jenkins
Project: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.2-snapshot_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.2-snapshot_build-artifacts-el7-x86_64/152/ Build Number: 152 Build Status: Fixed Triggered By: Started by timer

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 177 - Still Failing!

2018-02-01 Thread jenkins
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/177/ Build Number: 177 Build Status: Still Failing Triggered By: Started by timer - Changes Since Last

[oVirt Jenkins] ovirt-system-tests_he-basic-suite-master - Build # 190 - Failure!

2018-02-01 Thread jenkins
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/190/ Build Number: 190 Build Status: Failure Triggered By: Started by timer - Changes Since Last Succe

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.1 - Build # 171 - Still Failing!

2018-02-01 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/171/ Build Number: 171 Build Status: Still Failing Triggered By: Started by timer - Changes Since Last Succes

test failed due to out of free disk space

2018-02-01 Thread Lev Veyde
Hi, The system test here seems to fail on out of disk space: http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests_manual/2111/console The error it shows is: ( IOError: [Errno 28] No space left on device ) Can you please take a look? Thanks in advance, -- Lev Veyde Sof

[oVirt Jenkins] ovirt-system-tests_he-basic-ansible-suite-master - Build # 23 - Failure!

2018-02-01 Thread jenkins
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-master/23/ Build Number: 23 Build Status: Failure Triggered By: Started by timer - Changes S

[CQ]: 72018, 1 (ovirt-engine-extension-logger-log4j) failed "ovirt-master" system tests, but isn't the failure root cause

2018-02-01 Thread oVirt Jenkins
A system test invoked by the "ovirt-master" change queue including change 72018,1 (ovirt-engine-extension-logger-log4j) failed. However, this change seems not to be the root cause for this failure. Change 61244,2 (ovirt-engine- extension-logger-log4j) that this change depends on or is based on, was

[CQ]: 61244, 2 (ovirt-engine-extension-logger-log4j) failed "ovirt-master" system tests

2018-02-01 Thread oVirt Jenkins
Change 61244,2 (ovirt-engine-extension-logger-log4j) 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. Fo

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

2018-02-01 Thread oVirt Jenkins
A system test invoked by the "ovirt-master" change queue including change 87020,2 (cockpit-ovirt) failed. However, this change seems not to be the root cause for this failure. Change 87008,1 (cockpit-ovirt) that this change depends on or is based on, was detected as the cause of the testing failure

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #1234

2018-02-01 Thread jenkins
See Changes: [Sandro Bonazzola] ovirt-engine-yarn: re-align [Dafna Ron] ovirt-vmconsole - dropping fc24 [Sandro Bonazzola] ovirt-vmconsole: re-align

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

2018-02-01 Thread oVirt Jenkins
Change 86512,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 furthe

[CQ]: 87008,1 (cockpit-ovirt) failed "ovirt-master" system tests

2018-02-01 Thread oVirt Jenkins
Change 87008,1 (cockpit-ovirt) 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 abou

[CQ]: 86998,1 (ovirt-host-deploy) failed "ovirt-master" system tests

2018-02-01 Thread oVirt Jenkins
Change 86998,1 (ovirt-host-deploy) 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]: 83288, 1 (ovirt-engine-extension-logger-log4j) failed "ovirt-4.2" system tests

2018-02-01 Thread oVirt Jenkins
Change 83288,1 (ovirt-engine-extension-logger-log4j) 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 f

[CQ]: 76785,1 (ovirt-engine-yarn) failed "ovirt-4.2" system tests

2018-02-01 Thread oVirt Jenkins
Change 76785,1 (ovirt-engine-yarn) 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 abo

[JIRA] (OVIRT-1873) Vdsm fcraw builds fail because ovirt-imageio-common is not installed

2018-02-01 Thread Nir Soffer (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35734#comment-35734 ] Nir Soffer commented on OVIRT-1873: --- I fix the missing ovirt-imageio-common package, see: ht

Re: Vdsm fcraw builds fail because ovirt-imageio-common is not installed

2018-02-01 Thread Nir Soffer
I fix the missing ovirt-imageio-common package, see: https://gerrit.ovirt.org/#/c/87034/ But now it fails with mom: nothing provides mom >= 0.5.8 needed by vdsm-4.20.17-29.git89eb77538.fc28.x86_64 We are not ready yet for fcraw. I disabled the job again, will give us more time until jenkins confi

[CQ]: 82649, 2 (ovirt-image-uploader) failed "ovirt-master" system tests

2018-02-01 Thread oVirt Jenkins
Change 82649,2 (ovirt-image-uploader) 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 detai

[CQ]: 87027,2 (ovirt-engine) failed "ovirt-4.2" system tests

2018-02-01 Thread oVirt Jenkins
Change 87027,2 (ovirt-engine) 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 th

[CQ]: 87036, 1 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause

2018-02-01 Thread oVirt Jenkins
A system test invoked by the "ovirt-4.2" change queue including change 87036,1 (cockpit-ovirt) failed. However, this change seems not to be the root cause for this failure. Change 86648,1 (cockpit-ovirt) that this change depends on or is based on, was detected as the cause of the testing failures.

[CQ]: 87035, 1 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause

2018-02-01 Thread oVirt Jenkins
A system test invoked by the "ovirt-4.2" change queue including change 87035,1 (cockpit-ovirt) failed. However, this change seems not to be the root cause for this failure. Change 86648,1 (cockpit-ovirt) that this change depends on or is based on, was detected as the cause of the testing failures.

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

2018-02-01 Thread oVirt Jenkins
A system test invoked by the "ovirt-4.2" change queue including change 87014,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 o

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

2018-02-01 Thread oVirt Jenkins
A system test invoked by the "ovirt-4.2" change queue including change 87013,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 o

[JIRA] (OVIRT-1873) Vdsm fcraw builds fail because ovirt-imageio-common is not installed

2018-02-01 Thread Nir Soffer (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35733#comment-35733 ] Nir Soffer commented on OVIRT-1873: --- With the tested repo, the build fails with: 00:00:40.1

[CQ]: 87032, 1 (ovirt-hosted-engine-setup) failed "ovirt-4.2" system tests, but isn't the failure root cause

2018-02-01 Thread oVirt Jenkins
A system test invoked by the "ovirt-4.2" change queue including change 87032,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 o

[JIRA] (OVIRT-1873) Vdsm fcraw builds fail because ovirt-imageio-common is not installed

2018-02-01 Thread Nir Soffer (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35732#comment-35732 ] Nir Soffer commented on OVIRT-1873: --- The package comes from http://resources.ovirt.org. Loo

[CQ]: 86956, 3 (ovirt-hosted-engine-setup) failed "ovirt-4.2" system tests, but isn't the failure root cause

2018-02-01 Thread oVirt Jenkins
A system test invoked by the "ovirt-4.2" change queue including change 86956,3 (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 o

[JIRA] (OVIRT-1873) Vdsm fcraw builds fail because ovirt-imageio-common is not installed

2018-02-01 Thread Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35731#comment-35731 ] Barak Korren commented on OVIRT-1873: - [~nsof...@redhat.com] is there a repo configured wh

[CQ]: 77568,2 (ovirt-engine-nodejs) failed "ovirt-4.2" system tests

2018-02-01 Thread oVirt Jenkins
Change 77568,2 (ovirt-engine-nodejs) 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 a

[CQ]: 77568,2 (ovirt-engine-nodejs) failed "ovirt-4.1" system tests

2018-02-01 Thread oVirt Jenkins
Change 77568,2 (ovirt-engine-nodejs) 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 a

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

2018-02-01 Thread oVirt Jenkins
Change 86512,2 (ovirt-engine-nodejs-modules) 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 d

[CQ]: 83813,1 (ovirt-guest-agent) failed "ovirt-master" system tests

2018-02-01 Thread oVirt Jenkins
Change 83813,1 (ovirt-guest-agent) 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]: 87010, 1 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause

2018-02-01 Thread oVirt Jenkins
A system test invoked by the "ovirt-4.2" change queue including change 87010,1 (cockpit-ovirt) failed. However, this change seems not to be the root cause for this failure. Change 86648,1 (cockpit-ovirt) that this change depends on or is based on, was detected as the cause of the testing failures.

[CQ]: 87009, 1 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause

2018-02-01 Thread oVirt Jenkins
A system test invoked by the "ovirt-4.2" change queue including change 87009,1 (cockpit-ovirt) failed. However, this change seems not to be the root cause for this failure. Change 86648,1 (cockpit-ovirt) that this change depends on or is based on, was detected as the cause of the testing failures.

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

2018-02-01 Thread oVirt Jenkins
A system test invoked by the "ovirt-4.2" change queue including change 86996,1 (ovirt-host-deploy) failed. However, this change seems not to be the root cause for this failure. Change 86991,1 (ovirt-host-deploy) that this change depends on or is based on, was detected as the cause of the testing fa

[CQ]: 86997, 2 (ovirt-host-deploy) failed "ovirt-4.2" system tests, but isn't the failure root cause

2018-02-01 Thread oVirt Jenkins
A system test invoked by the "ovirt-4.2" change queue including change 86997,2 (ovirt-host-deploy) failed. However, this change seems not to be the root cause for this failure. Change 86991,1 (ovirt-host-deploy) that this change depends on or is based on, was detected as the cause of the testing fa

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

2018-02-01 Thread oVirt Jenkins
A system test invoked by the "ovirt-master" change queue including change 86983,3 (otopi) failed. However, this change seems not to be the root cause for this failure. Change 86679,4 (otopi) that this change depends on or is based on, was detected as the cause of the testing failures. This change

[CQ]: 82649,2 (ovirt-image-uploader) failed "ovirt-4.2" system tests

2018-02-01 Thread oVirt Jenkins
Change 82649,2 (ovirt-image-uploader) 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

[JIRA] (OVIRT-1873) Vdsm fcraw builds fail because ovirt-imageio-common is not installed

2018-02-01 Thread Nir Soffer (oVirt JIRA)
Nir Soffer created OVIRT-1873: - Summary: Vdsm fcraw builds fail because ovirt-imageio-common is not installed Key: OVIRT-1873 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1873 Project: oVirt - virtu

Vdsm fcraw builds fail because ovirt-imageio-common is not installed

2018-02-01 Thread Nir Soffer
We require the package: $ grep ovirt-imageio-common automation/check-patch.packages.fcraw ovirt-imageio-common Here are few failing builds, we have more: http://jenkins.ovirt.org/job/vdsm_master_check-patch-fcraw-x86_64/95/consoleFull http://jenkins.ovirt.org/job/vdsm_master_check-patch-fcraw-x8

[CQ]: 86991,1 (ovirt-host-deploy) failed "ovirt-4.2" system tests

2018-02-01 Thread oVirt Jenkins
Change 86991,1 (ovirt-host-deploy) 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 abo

[CQ]: 77568,2 (ovirt-engine-nodejs) failed "ovirt-4.1" system tests

2018-02-01 Thread oVirt Jenkins
Change 77568,2 (ovirt-engine-nodejs) 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 a

[ OST Failure Report ] [ oVirtMaster (otopi) ] [ 01-02-2018 ] [ 001_initialize_engine.initialize_engine/001_upgrade_engine.test_initialize_engine ]

2018-02-01 Thread Dafna Ron
Hi, We are failing initialize engine on both basic and upgrade suites. Can you please check? *Link and headline of suspected patches: https://gerrit.ovirt.org/#/c/86679/ - * *core: Check Sequence before/afterLink to Job:http://jenkin

[CQ]: 77568,2 (ovirt-engine-nodejs) failed "ovirt-4.2" system tests

2018-02-01 Thread oVirt Jenkins
Change 77568,2 (ovirt-engine-nodejs) 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 a

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

2018-02-01 Thread oVirt Jenkins
A system test invoked by the "ovirt-master" change queue including change 86961,1 (otopi) failed. However, this change seems not to be the root cause for this failure. Change 86679,4 (otopi) that this change depends on or is based on, was detected as the cause of the testing failures. This change

[CQ]: 86959,3 (ovirt-setup-lib) failed "ovirt-4.1" system tests

2018-02-01 Thread oVirt Jenkins
Change 86959,3 (ovirt-setup-lib) 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

[CQ]: 81104, 1 (ovirt-engine-wildfly-overlay) failed "ovirt-4.2" system tests

2018-02-01 Thread oVirt Jenkins
Change 81104,1 (ovirt-engine-wildfly-overlay) 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

[oVirt Jenkins] ovirt-appliance_ovirt-4.1-snapshot_build-artifacts-el7-x86_64 - Build # 422 - Still Failing!

2018-02-01 Thread jenkins
Project: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.1-snapshot_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.1-snapshot_build-artifacts-el7-x86_64/422/ Build Number: 422 Build Status: Still Failing Triggered By: Started by timer

[CQ]: 83813,1 (ovirt-guest-agent) failed "ovirt-4.2" system tests

2018-02-01 Thread oVirt Jenkins
Change 83813,1 (ovirt-guest-agent) 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 abo

Change in stdci-staging[master]: dummy change

2018-02-01 Thread review
>From Daniel Belenky : Daniel Belenky has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/128 ) Change subject: dummy change .. Patch Set 3: ci re-merge please -- To view, visit https://gerrit-staging

[CQ]: 86985, 2 (otopi) failed "ovirt-4.2" system tests, but isn't the failure root cause

2018-02-01 Thread oVirt Jenkins
A system test invoked by the "ovirt-4.2" change queue including change 86985,2 (otopi) failed. However, this change seems not to be the root cause for this failure. Change 86982,1 (otopi) that this change depends on or is based on, was detected as the cause of the testing failures. This change had

[CQ]: 86984, 2 (otopi) failed "ovirt-4.2" system tests, but isn't the failure root cause

2018-02-01 Thread oVirt Jenkins
A system test invoked by the "ovirt-4.2" change queue including change 86984,2 (otopi) failed. However, this change seems not to be the root cause for this failure. Change 86982,1 (otopi) that this change depends on or is based on, was detected as the cause of the testing failures. This change had

[ OST Failure Report ] [ oVirt Master (vdsm) ] [ 01-02-2018 ] [ 002_bootstrap.verify_add_all_hosts ]

2018-02-01 Thread Dafna Ron
Hi, We failed cq test 002_bootstrap.verify_add_all_hosts for Master vdsm project. Looking at the log, vdsm cannot find master storage domain and engine puts the host on non-operational state. Although on the surface the patch seems to be related, the master storage domain is iscsi whole the patc

[oVirt Jenkins] ovirt-appliance_master_build-artifacts-el7-x86_64 - Build # 692 - Fixed!

2018-02-01 Thread jenkins
Project: http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86_64/692/ Build Number: 692 Build Status: Fixed Triggered By: Started by timer - Changes

[CQ]: 86982,1 (otopi) failed "ovirt-4.2" system tests

2018-02-01 Thread oVirt Jenkins
Change 86982,1 (otopi) 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 chang

[CQ]: 86978, 1 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause

2018-02-01 Thread oVirt Jenkins
A system test invoked by the "ovirt-4.2" change queue including change 86978,1 (cockpit-ovirt) failed. However, this change seems not to be the root cause for this failure. Change 86648,1 (cockpit-ovirt) that this change depends on or is based on, was detected as the cause of the testing failures.

[CQ]: 69668,7 (vdsm) failed "ovirt-master" system tests

2018-02-01 Thread oVirt Jenkins
Change 69668,7 (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 cha

[CQ]: 86977, 1 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause

2018-02-01 Thread oVirt Jenkins
A system test invoked by the "ovirt-4.2" change queue including change 86977,1 (cockpit-ovirt) failed. However, this change seems not to be the root cause for this failure. Change 86648,1 (cockpit-ovirt) that this change depends on or is based on, was detected as the cause of the testing failures.

[JIRA] (OVIRT-1872) Jenkins outage 01.02.2018

2018-02-01 Thread Evgheni Dereveanchin (oVirt JIRA)
Evgheni Dereveanchin created OVIRT-1872: --- Summary: Jenkins outage 01.02.2018 Key: OVIRT-1872 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1872 Project: oVirt - virtualization made easy

[JIRA] (OVIRT-1872) Jenkins outage 01.02.2018

2018-02-01 Thread Evgheni Dereveanchin (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgheni Dereveanchin reassigned OVIRT-1872: --- Assignee: Evgheni Dereveanchin (was: infra) > Jenkins outage 01.02.2018 >

[CQ]: 86968, 1 (ovirt-engine-wildfly) failed "ovirt-4.2" system tests, but isn't the failure root cause

2018-02-01 Thread oVirt Jenkins
A system test invoked by the "ovirt-4.2" change queue including change 86968,1 (ovirt-engine-wildfly) failed. However, this change seems not to be the root cause for this failure. Change 83154,4 (ovirt-engine-wildfly) that this change depends on or is based on, was detected as the cause of the test

[CQ]: 86967, 1 (ovirt-hosted-engine-setup) failed "ovirt-4.2" system tests, but isn't the failure root cause

2018-02-01 Thread oVirt Jenkins
A system test invoked by the "ovirt-4.2" change queue including change 86967,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 o

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 176 - Still Failing!

2018-02-01 Thread jenkins
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/176/ Build Number: 176 Build Status: Still Failing Triggered By: Started by timer - Changes Since Last

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.1 - Build # 170 - Still Failing!

2018-02-01 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/170/ Build Number: 170 Build Status: Still Failing Triggered By: Started by timer - Changes Since Last Succes

[oVirt CI] standard-enqueue - Build #9475 - FAILURE!

2018-02-01 Thread jenkins
Build: http://jenkins.ovirt.org/job/standard-enqueue/9475/ Build Name: #9475 Build Description: Gerrit: 86918 [ovirt-engine] Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/86918 - title: core: Split log message by new line - project: ovirt-engine - branch: master - author: Ala Hino _

[oVirt CI] standard-enqueue - Build #9474 - FAILURE!

2018-02-01 Thread jenkins
Build: http://jenkins.ovirt.org/job/standard-enqueue/9474/ Build Name: #9474 Build Description: Gerrit: 82649 - ovirt-image-uploader (4.0, 4.1, 4.2, master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/82649 - title: automation: drop snapshot repos - project: ovirt-image-uploader -

[JIRA] (OVIRT-1871) Wrong target milestone check on new 4.2 branches for ovirt-host-deploy

2018-02-01 Thread sbonazzo (oVirt JIRA)
sbonazzo created OVIRT-1871: --- Summary: Wrong target milestone check on new 4.2 branches for ovirt-host-deploy Key: OVIRT-1871 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1871 Project: oVirt - virtual

[JIRA] (OVIRT-1871) Wrong target milestone check on new 4.2 branches for ovirt-host-deploy

2018-02-01 Thread sbonazzo (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sbonazzo updated OVIRT-1871: Epic Link: OVIRT-400 > Wrong target milestone check on new 4.2 branches for ovirt-host-deploy > --