[oVirt Jenkins] ovirt-system-tests_compat-3.6-suite-master - Build # 281 - Still Failing!

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

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

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

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

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

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-4.2 - Build # 428 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-4.2/428/ Build Number: 428 Build Status: Still Failing Triggered By: Started by timer - Changes

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

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

[oVirt Jenkins] ovirt-system-tests_he-basic-suite-4.2 - Build # 686 - Still Failing!

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

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-4.2 - Build # 429 - 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/429/ Build Number: 429 Build Status: Failure Triggered By: Started by timer - Changes Since Last

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 592 - Still Failing!

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

[oVirt Jenkins] ovirt-system-tests_compat-4.1-suite-master - Build # 281 - Still Failing!

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

[oVirt Jenkins] ovirt-system-tests_compat-4.0-suite-master - Build # 281 - Still Failing!

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

Build failed in Jenkins: ovirt_4.1_publish-rpms_nightly #718

See -- Started by timer [EnvInject] - Loading node environment variables. Building on master in workspace

oVirt infra daily report - unstable production jobs - 622

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/622//artifact/exported-artifacts/upstream_report.html Cheers, Jenkins

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

Re: [ovirt-devel] jobs failure due to same package version with different checksum

Thanks Dafna, I will do that, will update the thread once it will be fixed. Thanks, Maor On Tue, Oct 23, 2018 at 5:29 PM Dafna Ron wrote: > Hi, > > We have been having failure in master for different projects due to > package ovirt-ansible-disaster-recovery-1.1.2-1.el7.noarch.rpm. > > It

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

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

[oVirt Jenkins] ovirt-system-tests_compat-3.6-suite-master - Build # 280 - Still Failing!

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

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

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

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-4.2 - Build # 427 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-4.2/427/ Build Number: 427 Build Status: Still Failing Triggered By: Started by timer - Changes

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

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

[oVirt Jenkins] ovirt-system-tests_he-basic-suite-4.2 - Build # 685 - Still Failing!

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

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-4.2 - Build # 428 - Fixed!

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

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 591 - Still Failing!

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

[oVirt Jenkins] ovirt-system-tests_compat-4.1-suite-master - Build # 280 - Still Failing!

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

[oVirt Jenkins] ovirt-system-tests_compat-4.0-suite-master - Build # 280 - Still Failing!

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

[JIRA] (OVIRT-2558) containerize more bare metals

Evgheni Dereveanchin created OVIRT-2558: --- Summary: containerize more bare metals Key: OVIRT-2558 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2558 Project: oVirt - virtualization made easy

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

https://ovirt-jira.atlassian.net/browse/OVIRT-2555 On Tue, Oct 23, 2018 at 3:40 PM oVirt Jenkins wrote: > A system test invoked by the "ovirt-master" change queue including change > 95011,1 (otopi) failed. However, this change seems not to be the root > cause for > this failure. Change 91669,5

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

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

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

jobs failure due to same package version with different checksum

Hi, We have been having failure in master for different projects due to package ovirt-ansible-disaster-recovery-1.1.2-1.el7.noarch.rpm. It seems the package had been changed without a new version set which means we have the same exact package with two different checksum (one in 4.2 and one in

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

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

[oVirt Jenkins] ovirt-system-tests_compat-3.6-suite-master - Build # 279 - Still Failing!

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

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

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

[oVirt Jenkins] ovirt-node-ng-image_master_build-artifacts-fc28-x86_64 - Build # 93 - Fixed!

Project: http://jenkins.ovirt.org/job/ovirt-node-ng-image_master_build-artifacts-fc28-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-node-ng-image_master_build-artifacts-fc28-x86_64/93/ Build Number: 93 Build Status: Fixed Triggered By: Started by timer

[JIRA] (OVIRT-2557) upgrade jenkins.ovirt.org to 2.138.2 LTS

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgheni Dereveanchin reassigned OVIRT-2557: --- Assignee: Evgheni Dereveanchin (was: infra) > upgrade jenkins.ovirt.org

[JIRA] (OVIRT-2557) upgrade jenkins.ovirt.org to 2.138.2 LTS

Evgheni Dereveanchin created OVIRT-2557: --- Summary: upgrade jenkins.ovirt.org to 2.138.2 LTS Key: OVIRT-2557 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2557 Project: oVirt -

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

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

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-4.2 - Build # 426 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-4.2/426/ Build Number: 426 Build Status: Still Failing Triggered By: Started by timer - Changes

[JIRA] (OVIRT-2556) kubevirt test runs and nested docker issue

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=38269#comment-38269 ] Gal Ben Haim commented on OVIRT-2556: - [~lbednar] FYI > kubevirt test runs and nested docker issue >

[JIRA] (OVIRT-2556) kubevirt test runs and nested docker issue

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=38268#comment-38268 ] Gal Ben Haim commented on OVIRT-2556: - I've killed the old STDCI container and spawned a new one instead.

[JIRA] (OVIRT-2555) failures on ovirt-master failed due to access to resources

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgheni Dereveanchin reassigned OVIRT-2555: --- Assignee: Evgheni Dereveanchin (was: infra) > failures on ovirt-master

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

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

[JIRA] (OVIRT-2555) failures on ovirt-master failed due to access to resources

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=38264#comment-38264 ] Dafna Ron commented on OVIRT-2555: -- I was able to wget and repoquery the package:

[JIRA] (OVIRT-2556) kubevirt test runs and nested docker issue

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=38263#comment-38263 ] Roman Mohr commented on OVIRT-2556: --- Ok, let me see if it looks better now. For reference here a very bad

Re: [CQ]: 95058,2 (cockpit-ovirt) failed "ovirt-master" system tests

https://ovirt-jira.atlassian.net/browse/OVIRT-2555 On Tue, Oct 23, 2018 at 9:49 AM oVirt Jenkins wrote: > Change 95058,2 (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

[JIRA] (OVIRT-2556) kubevirt test runs and nested docker issue

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=38261#comment-38261 ] Gal Ben Haim commented on OVIRT-2556: - All the jobs that failed run on

[JIRA] (OVIRT-2555) failures on ovirt-master failed due to access to resources

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=38260#comment-38260 ] Dafna Ron commented on OVIRT-2555: -- https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10903/ >

[oVirt Jenkins] ovirt-system-tests_he-basic-suite-4.2 - Build # 684 - Still Failing!

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

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-4.2 - Build # 427 - 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/427/ Build Number: 427 Build Status: Still Failing Triggered By: Started by timer - Changes Since Last

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 590 - 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/590/ Build Number: 590 Build Status: Failure Triggered By: Started by timer - Changes Since Last Success:

[oVirt Jenkins] ovirt-system-tests_compat-4.0-suite-master - Build # 279 - Still Failing!

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

[oVirt Jenkins] ovirt-system-tests_compat-4.1-suite-master - Build # 279 - Still Failing!

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

[JIRA] (OVIRT-2556) kubevirt test runs and nested docker issue

Roman Mohr created OVIRT-2556: - Summary: kubevirt test runs and nested docker issue Key: OVIRT-2556 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2556 Project: oVirt - virtualization made easy

[CQ]: 95058,2 (cockpit-ovirt) failed "ovirt-master" system tests

Change 95058,2 (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

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

See ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement:

Re: [CQ]: b98ef7a (ovirt-ansible-disaster-recovery) failed "ovirt-master" system tests

https://ovirt-jira.atlassian.net/browse/OVIRT-2555 On Tue, Oct 23, 2018 at 12:57 AM oVirt Jenkins wrote: > Change b98ef7a (ovirt-ansible-disaster-recovery) is probably the reason > behind > recent system test failures in the "ovirt-master" change queue and needs > to be > fixed. > > This change

[JIRA] (OVIRT-2555) failures on ovirt-master failed due to access to resources

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=38259#comment-38259 ] Dafna Ron commented on OVIRT-2555: -- https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10901/ >

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

https://ovirt-jira.atlassian.net/browse/OVIRT-2555 On Tue, Oct 23, 2018 at 12:10 AM oVirt Jenkins wrote: > A system test invoked by the "ovirt-master" change queue including change > 95011,1 (otopi) failed. However, this change seems not to be the root > cause for > this failure. Change 91669,5

[JIRA] (OVIRT-2555) failures on ovirt-master failed due to access to resources

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=38258#comment-38258 ] Dafna Ron commented on OVIRT-2555: -- second failure for otopi:

[JIRA] (OVIRT-2555) failures on ovirt-master failed due to access to resources

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dafna Ron updated OVIRT-2555: - Summary: failures on ovirt-master failed due to access to resources (was:

[JIRA] (OVIRT-2555) ovirt-ansible-v2v-conversion-host on ovirt-master failed due to access to resources

Dafna Ron created OVIRT-2555: Summary: ovirt-ansible-v2v-conversion-host on ovirt-master failed due to access to resources Key: OVIRT-2555 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2555

Re: [CQ]: 74b0e9e (ovirt-ansible-v2v-conversion-host) failed "ovirt-master" system tests, but isn't the failure root cause

https://ovirt-jira.atlassian.net/browse/OVIRT-2555 re-triggered On Mon, Oct 22, 2018 at 11:19 PM oVirt Jenkins wrote: > A system test invoked by the "ovirt-master" change queue including change > 74b0e9e (ovirt-ansible-v2v-conversion-host) failed. However, this change > seems > not to be the

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

https://ovirt-jira.atlassian.net/browse/OVIRT-2554 On Mon, Oct 22, 2018 at 9:24 PM oVirt Jenkins wrote: > A system test invoked by the "ovirt-master" change queue including change > 95003,3 (pthreading) failed. However, this change seems not to be the root > cause for this failure. Change

[JIRA] (OVIRT-2554) failure in master pthreading project on test 004_basic_sanity.next_run_unplug_cpu with no clear logs

Dafna Ron created OVIRT-2554: Summary: failure in master pthreading project on test 004_basic_sanity.next_run_unplug_cpu with no clear logs Key: OVIRT-2554 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2554

[JENKINS] Failed to setup proejct kubevirt_common-templates_standard-check-pr

Failed to run project_setup.sh for: #132 common-templates [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

Failed to run project_setup.sh for: #2347 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

Failed to run project_setup.sh for: #2347 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

Failed to run project_setup.sh for: #2347 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

Failed to run project_setup.sh for: #2347 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[oVirt Jenkins] ovirt-node-ng-image_master_build-artifacts-el7-x86_64 - Build # 92 - Fixed!

Project: http://jenkins.ovirt.org/job/ovirt-node-ng-image_master_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-node-ng-image_master_build-artifacts-el7-x86_64/92/ Build Number: 92 Build Status: Fixed Triggered By: Started by timer -

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

Failed to run project_setup.sh for: #2347 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

Failed to run project_setup.sh for: #2347 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[JENKINS] Failed to setup proejct kubevirt_common-templates_standard-check-pr

Failed to run project_setup.sh for: #131 common-templates [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

Failed to run project_setup.sh for: #2346 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

Failed to run project_setup.sh for: #2346 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

Failed to run project_setup.sh for: #2346 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

Failed to run project_setup.sh for: #2346 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

Failed to run project_setup.sh for: #2346 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

Failed to run project_setup.sh for: #2346 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

Failed to run project_setup.sh for: #2346 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

Failed to run project_setup.sh for: #2346 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[JENKINS] Failed to setup proejct kubevirt_common-templates_standard-check-pr

Failed to run project_setup.sh for: #130 common-templates [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

Failed to run project_setup.sh for: #2345 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[JIRA] (OVIRT-2549) master ovirt-engine fails on missing package

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dafna Ron updated OVIRT-2549: - Resolution: Fixed Status: Done (was: To Do) > master ovirt-engine fails on missing package >

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

Failed to run project_setup.sh for: #2345 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[JIRA] (OVIRT-2549) master ovirt-engine fails on missing package

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=38257#comment-38257 ] Dafna Ron commented on OVIRT-2549: -- thanks you [~sbona...@redhat.com] This issue is resolved. > master

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

Failed to run project_setup.sh for: #2345 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

Failed to run project_setup.sh for: #2345 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

Failed to run project_setup.sh for: #2345 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

Failed to run project_setup.sh for: #2345 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

Failed to run project_setup.sh for: #2345 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

Failed to run project_setup.sh for: #2345 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

Failed to run project_setup.sh for: #2344 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

Failed to run project_setup.sh for: #2344 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

Failed to run project_setup.sh for: #2344 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

Failed to run project_setup.sh for: #2344 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

Failed to run project_setup.sh for: #2344 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

Failed to run project_setup.sh for: #2344 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

Failed to run project_setup.sh for: #2343 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

Failed to run project_setup.sh for: #2341 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on

  1   2   >