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

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

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 117 - 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/117/ Build Number: 117 Build Status: Still Failing Triggered By: Started by timer - Changes Since

Jenkins build is back to normal : system-sync_mirrors-epel-el6-x86_64 #987

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

[oVirt Jenkins] ovirt-appliance_ovirt-4.1-pre_build-artifacts-el7-x86_64 - Build # 126 - Failure!

Project: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.1-pre_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.1-pre_build-artifacts-el7-x86_64/126/ Build Number: 126 Build Status: Failure Triggered By: Started by timer

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

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

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #986

See Changes: [Anton Marchukov] Enabled repoman builds on Fedora 27. -- Started by timer [EnvInject] - Loading node environment variables. Building

oVirt infra weekly meeting notes 06.12.2017

Hi everyone, Please find the topics of this week's infra meeting below: PHX DC: - Overview of infra and documentation - PHX upgrade to 4.2 progressing , some more bugs

Re: [ovirt-devel] [ OST Failure Report ] [ oVirtMaster ] [ 07-11-2017 ] [007_sd_reattach.deactivate_storage_domain ]

On Thu, Dec 7, 2017 at 1:30 PM, Eyal Shenitzky wrote: > I think that the maybe the QE can share their methods on how to avoid > those issues. > From what I remember, before deactivating storage domain they make sure > that there are no running tasks related to > the storage

Re: [ovirt-devel] [ OST Failure Report ] [ oVirtMaster ] [ 07-11-2017 ] [007_sd_reattach.deactivate_storage_domain ]

I think that the maybe the QE can share their methods on how to avoid those issues. >From what I remember, before deactivating storage domain they make sure that there are no running tasks related to the storage domain. On Thu, Dec 7, 2017 at 1:22 PM, Yaniv Kaul wrote: > > >

Re: [ovirt-devel] [ OST Failure Report ] [ oVirtMaster ] [ 07-11-2017 ] [007_sd_reattach.deactivate_storage_domain ]

On Thu, Dec 7, 2017 at 1:12 PM, Dafna Ron wrote: > Maor, I either need to get new glasses or a magnifier glass to read what > you wrote :-P > when you say running tasks - these are actually running tasks that may be > running because of other tests in ost - correct? wouldn't

Re: [ovirt-devel] [ OST Failure Report ] [ oVirtMaster ] [ 07-11-2017 ] [007_sd_reattach.deactivate_storage_domain ]

Maor, I either need to get new glasses or a magnifier glass to read what you wrote :-P when you say running tasks - these are actually running tasks that may be running because of other tests in ost - correct? wouldn't killing or blocking those can cause other tests to fail? On 12/07/2017 11:06

Re: [ovirt-devel] [ OST Failure Report ] [ oVirtMaster ] [ 07-11-2017 ] [007_sd_reattach.deactivate_storage_domain ]

CANNOT_DEACTIVATE_DOMAIN_WITH_TASKS is a known issue, the problem is that we might have tasks which will start running internally using scheduling (like OVF_UPDATE) and we can't really know how much time every task will take until it will end. Even if we check that there are no running tasks it

[JIRA] (OVIRT-1788) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=35473#comment-35473 ] Barak Korren commented on OVIRT-1788: - [~gsher...@redhat.com] I don't know enough about how to use

[ OST Failure Report ] [ oVirtMaster ] [ 07-11-2017 ] [007_sd_reattach.deactivate_storage_domain ]

Hi, We had a failure on master basic suite for test 007_sd_reattach.deactivate_storage_domain. The failure was that we failed to deactivate domain due to running tasks. It does not seem to be related to the patch it was testing and I think that the test itself needs to be modified to check

Jenkins build is back to normal : system-sync_mirrors-epel-el6-x86_64 #985

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

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #984

See Changes: [Yedidyah Bar David] wgt: Fix excludes -- Started by timer [EnvInject] - Loading node environment variables. Building remotely on

Jenkins build is back to normal : system-sync_mirrors-fedora-base-fcraw-x86_64 #191

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

Re: [ovirt-users] [ANN] oVirt 4.2.0 First Candidate Release is now available for testing

On Tue, Dec 5, 2017 at 5:10 PM, Sandro Bonazzola wrote: > The oVirt Project is pleased to announce the availability of the First > Candidate Release of oVirt 4.2.0, as of December 5th, 2017 > > This is pre-release software. This pre-release should not to be used in >