[CQ]: 92318, 9 (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 92318,9 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 92567,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-master - Build # 284 - Fixed!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master/284/ Build Number: 284 Build Status: Fixed Triggered By: Started by timer - Changes

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 301 - Failure!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/301/ Build Number: 301 Build Status: Failure Triggered By: Started by timer - Changes Since Last Success:

[CQ]: 92587, 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 92587,3 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 92567,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-4.2 - Build # 75 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-4.2/75/ Build Number: 75 Build Status: Still Failing Triggered By: Started by timer - Changes Since Last

[oVirt Jenkins] ovirt-system-tests_network-suite-master - Build # 341 - Still Failing!

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

[CQ]: 92149, 13 (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 92149,13 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 92567,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

[JIRA] (OVIRT-2263) add uxd to oVirt github developers group

Greg Sheremeta created OVIRT-2263: - Summary: add uxd to oVirt github developers group Key: OVIRT-2263 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2263 Project: oVirt - virtualization made easy

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

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master/283/ Build Number: 283 Build Status: Failure Triggered By: Started by timer - Changes

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

Change 92567,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

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-4.2 - Build # 74 - Failure!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-4.2/74/ Build Number: 74 Build Status: Failure Triggered By: Started by timer - Changes Since Last Success:

[CQ]: 92313,2 (vdsm) failed "ovirt-4.2" system tests

Change 92313,2 (vdsm) 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

[oVirt Jenkins] ovirt-system-tests_network-suite-master - Build # 340 - Failure!

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

[JIRA] (OVIRT-2255) build aborted on time out

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=37291#comment-37291 ] Gal Ben Haim commented on OVIRT-2255: - # attach_vm_network_to_host_0_static_config: Success (in 1:08:46)

[JIRA] (OVIRT-2231) QEMU can't access "/home/jenkins/*" on FC28 slaves.

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gal Ben Haim updated OVIRT-2231: Assignee: Gal Ben Haim (was: infra) Status: In Progress (was: To Do) > QEMU can't access

oVirt infra weekly meeting notes 27.06.2018

Hi everyone, Please find the topics of this week's infra meeting below: *PHX - Jenkins- Security advisory out for several plugins OVIRT-2262 - Headers need to be added before next restart OVIRT-2199

[oVirt Jenkins] ovirt-node-ng_master_build-artifacts-el7-x86_64 - Build # 839 - Failure!

Project: http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64/839/ Build Number: 839 Build Status: Failure Triggered By: Started by timer - Changes

[JIRA] (OVIRT-2259) fc28: Failed to add ovirt-host: "The key algorithm 'EC' is not supported"

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=37290#comment-37290 ] danken commented on OVIRT-2259: --- I don't really understand the problem, nice [~nsof...@redhat.com] reports that

[JIRA] (OVIRT-2181) Release lago-ovirt for fc28

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eyal Edri updated OVIRT-2181: - Assignee: Gal Ben Haim (was: infra) Status: In Progress (was: To Do) Looks like work started as

[JIRA] (OVIRT-2256) Install the Parametrized Remote Trigger plugin

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgheni Dereveanchin reassigned OVIRT-2256: --- Assignee: Evgheni Dereveanchin (was: infra) > Install the Parametrized

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

Hi, Can you please take a look at the build-artifacts job? https://jenkins.ovirt.org/job/ovirt-appliance_standard-on-merge/3 *08:29:55* [build-artifacts.el7.x86_64] ERRORinternal error: process exited while connecting to monitor: 2018-06-27T08:29:55.518374Z qemu-system-x86_64: -drive

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

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

[JIRA] (OVIRT-2262) Apply fixes for Jenkins Security Advisory 2018-06-25

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgheni Dereveanchin reassigned OVIRT-2262: --- Assignee: Evgheni Dereveanchin (was: infra) > Apply fixes for Jenkins

[JIRA] (OVIRT-2262) Apply fixes for Jenkins Security Advisory 2018-06-25

Evgheni Dereveanchin created OVIRT-2262: --- Summary: Apply fixes for Jenkins Security Advisory 2018-06-25 Key: OVIRT-2262 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2262 Project: oVirt -

[JIRA] (OVIRT-2259) fc28: Failed to add ovirt-host: "The key algorithm 'EC' is not supported"

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=37281#comment-37281 ] Martin Perina commented on OVIRT-2259: -- The only thing that came to my mind is to enable the same SSH

[JIRA] (OVIRT-2259) fc28: Failed to add ovirt-host: "The key algorithm 'EC' is not supported"

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=37280#comment-37280 ] Gal Ben Haim commented on OVIRT-2259: - [~mwperina] Is there any temporary workaround for this issue? I

[JIRA] (OVIRT-2259) fc28: Failed to add ovirt-host: "The key algorithm 'EC' is not supported"

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sbonazzo updated OVIRT-2259: External issue ID: https://bugzilla.redhat.com/show_bug.cgi?id=1591801 Status: Blocked

[JIRA] (OVIRT-2259) fc28: Failed to add ovirt-host: "The key algorithm 'EC' is not supported"

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=37279#comment-37279 ] sbonazzo commented on OVIRT-2259: - For reference, bugzilla is

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 518 - Fixed!

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/518/ Build Number: 518 Build Status: Fixed Triggered By: Started by timer - Changes Since Last