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

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

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

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

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

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

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

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

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

[CQ]: 84760,1 (cockpit-ovirt) failed "ovirt-4.2" system tests

Change 84760,1 (cockpit-ovirt) 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]: 84758, 1 (ovirt-engine-dashboard) failed "ovirt-master" system tests, but isn't the failure root cause

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

OST Networking suite -- artifacts aren't collected.

Hey guys, I have a weird problem with our new OST suite. Although I copy certain directories to ../ovirt-system-tests/exported-artifacts (i.e. root dir/exported-artifacts), they are not being collected. Running the suite via mock, I can see that the directory is present with the logs (plus some

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

Change 84744,3 (ovirt-engine-dashboard) 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]: 84711,1 (cockpit-ovirt) failed "ovirt-4.1" system tests

Change 84711,1 (cockpit-ovirt) 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

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

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgheni Dereveanchin reassigned OVIRT-1783: --- Assignee: Dafna Ron (was: infra) > Please create new repositories on

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

I doubt that patch has anything to do with ovirt-imageio not starting. Daniel/Nir - any insight? On Mon, Nov 27, 2017 at 5:11 PM, Dafna Ron wrote: > *Hi, * > > * We have a failure reported in ovirt 4.1 on ovirt-imageio not starting > and causing initialize_engine to fail I am

[ OST Failure Report ] [ oVirt 4.1 ] [ 27-11-2017] [ 001_initialize_engine.test_initialize_engine ]

** *Hi*, ** * ** We have a failure reported in ovirt 4.1**on ovirt-imageio not starting and causing initialize_engine to fail I am not sure the reported patch is related**but it was reported by cq as the cause of the failure. Link and headline of suspected patches: Renamed

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

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

[CQ]: 84520,1 (cockpit-ovirt) failed "ovirt-4.1" system tests

Change 84520,1 (cockpit-ovirt) 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

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

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=35398#comment-35398 ] Martin Perina commented on OVIRT-1783: -- engine-setup roles will most probably miss oVirt 4.2 RC build,

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

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=35397#comment-35397 ] Dafna Ron commented on OVIRT-1783: -- I'll look at the instructions and ask help if needed. what is the priory

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

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=35396#comment-35396 ] eyal edri commented on OVIRT-1783: -- [~dron] can you handle it or you need help from [~ederevea] ? The

Jenkins build is back to stable : ovirt_master_publish-rpms_nightly #787

See ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

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

Build: http://jenkins.ovirt.org/job/standard-enqueue/7418/ Build Name: #7418 Build Description: Gerrit: 83614 - ovirt-engine (3.6) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/83614 - title: packaging: bin: Tool to help upgrade 3.5/el6 hosted-engine hosts directly to 3.6/el7 -

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

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=35395#comment-35395 ] Martin Perina commented on OVIRT-1783: -- Let's start with two of us to keep aligned with other roles, if

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

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Machacek updated OVIRT-1783: -- Description: Please create following repositories: ovirt-ansible-engine-setup

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

Ondra Machacek created OVIRT-1783: - Summary: Please create new repositories on ovirt github for new Ansible roles Key: OVIRT-1783 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1783 Project: