[CQ]: 86810, 1 (imgbased) 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 86810,1 (imgbased) failed. However, this change seems not to be the root cause for this failure. Change 86773,1 (imgbased) that this change depends on or is based on, was detected as the cause of the testing failures. This

[CQ]: 86811, 1 (imgbased) 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 86811,1 (imgbased) failed. However, this change seems not to be the root cause for this failure. Change 86773,1 (imgbased) that this change depends on or is based on, was detected as the cause of the testing failures. This

[CQ]: 86818, 1 (cockpit-ovirt) 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 86818,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]: 86819, 2 (cockpit-ovirt) 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 86819,2 (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]: 82234,1 (vcredist-x86) failed "ovirt-4.2" system tests

Change 82234,1 (vcredist-x86) 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]: 86820, 1 (cockpit-ovirt) 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 86820,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.

[oVirt Jenkins] ovirt-system-tests_performance-suite-master - Build # 76 - Failure!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_performance-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_performance-suite-master/76/ Build Number: 76 Build Status: Failure Triggered By: Started by timer, Started by timer -

[CQ]: 82632,1 (py2exe-py2.7) failed "ovirt-4.2" system tests

Change 82632,1 (py2exe-py2.7) 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]: 82234,1 (vcredist-x86) failed "ovirt-master" system tests

Change 82234,1 (vcredist-x86) 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]: 82667,1 (pywin32-py2.7) failed "ovirt-4.2" system tests

Change 82667,1 (pywin32-py2.7) 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

[ OST Failure Report ] [ oVirt Master (vcredist-x86) ] [ 26-01-2018 ] [ 002_bootstrap.verify_add_all_hosts ]

Hi, We had a failure on test 002_bootstrap.verify_add_all_hosts in Ovirt Master I don't think the patch reported is related to the issue. >From what I can see, the host was locked when we tried to query its status and since we couldn't fence the host we exited in timeout. I do not think the

[CQ]: 82234,1 (vcredist-x86) failed "ovirt-4.2" system tests

Change 82234,1 (vcredist-x86) 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]: 80073, 2 (ovirt-js-dependencies) failed "ovirt-4.2" system tests

Change 80073,2 (ovirt-js-dependencies) 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

[CQ]: 82386, 1 (nsis-simple-service-plugin) failed "ovirt-4.2" system tests

Change 82386,1 (nsis-simple-service-plugin) 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

[JIRA] (OVIRT-1863) Service Alert: foreman/HTTP tcp connection going up and down

Dafna Ron created OVIRT-1863: Summary: Service Alert: foreman/HTTP tcp connection going up and down Key: OVIRT-1863 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1863 Project: oVirt - virtualization

[oVirt Jenkins] ovirt-appliance_master_build-artifacts-el7-x86_64 - Build # 686 - Still Failing!

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/686/ Build Number: 686 Build Status: Still Failing Triggered By: Started by timer

[CQ]: 82638,1 (python-windows) failed "ovirt-4.2" system tests

Change 82638,1 (python-windows) 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]: 82386, 1 (nsis-simple-service-plugin) failed "ovirt-4.1" system tests

Change 82386,1 (nsis-simple-service-plugin) 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

[JIRA] (OVIRT-1863) Service Alert: foreman/HTTP tcp connection going up and down

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgheni Dereveanchin reassigned OVIRT-1863: --- Assignee: Evgheni Dereveanchin (was: infra) > Service Alert: foreman/HTTP

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

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

[oVirt Jenkins] ovirt-system-tests_performance-suite-master - Build # 77 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_performance-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_performance-suite-master/77/ Build Number: 77 Build Status: Still Failing Triggered By: Started by timer - Changes

[oVirt Jenkins] ovirt-system-tests_he-basic-ansible-suite-master - Build # 17 - Still Failing!

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/17/ Build Number: 17 Build Status: Still Failing Triggered By: Started by timer -